Describe the bug
ui/notifications/tool-input is specced as
{
jsonrpc: "2.0",
method: "ui/notifications/tool-input",
params: {
arguments: Record<string, unknown> // Tool input arguments
}
}
Tools on OAI do not require tool arguments to be given as objects -- they can be raw strings. This can lead to better tool calling fidelity since it avoids various escaping issues that models trip up on in JSON calling, especially with nested strings.
However, arguments to such tools cannot be represented in ui/notifications/tool-input because it requires an object for its arguments.
To Reproduce
Attempt to implement apps in a system that allows
Expected behavior
We should be able to model OAI custom tools in this call. I suggest just making arguments unknown.
Logs
N/A
Additional context
N/A