FunctionDeclarationSchema is too terse and needs to support valid additional JSONSchema definitions

[mattgi]

Description of the bug:

additionalProperties is not an allowed field to include for a parameter, nor is oneOf (or an array) of Types. It is also not possible to omit the type. All of these variations are valid JSONSchema property definitions.

This limits the values to being known and makes it difficult to utilize function calling for something like an object of React Props or something that is quite dynamic.

Actual vs expected behavior:

Add additionalProperties: true as a valid field for function params.
This should be treated equivalent to { [key:string]: any; }

Any other information you'd like to share?

No response

[krishnaagrawal7508]

hey, I would like to work on this issue, can u assign me this issue.

[mewanDimalsha]

I’ve been digging into the Python SDK and reviewing both the codebase and the documentation (e.g. API Docs). I noticed something that stood out: there’s no mention of additionalProperties anywhere. From what I can see, only the existing types are referenced across the board, with no discussion of additionalProperties or similar schema features like oneOf.