Description
Is your feature request related to a problem? Please describe.
When I am experimenting with different LLMs via chat I give them my tool description (in a format they expect) and then make them role-play with me executing my tool, basically doing E2E testing on practical examples.
Describe the solution you'd like
Single click paste button to enter data directly into a tool.
Ingesting arguments data through (forgiving) JSON parser would be optimal, so we don't get bogged down by tiny formatting bikeshedding side tangents while experimenting, if LLM generates less than perfect JSON (unquoted keys, single quoted keys, wrong escapes etc...).
Describe alternatives you've considered
Using a MCP playwright server which would inception-like control another MCP Inspector instance, converting raw data into input field data and submitting with one click. But at this point, it is less code and work to just create our own UI and skip the middleman.
Additional context
It is tedious to copy paste one line at a time, clicking checkboxes etc... a "paste JSON" button would be perfect (automatically ingesting clipboard data into inputs).
UI's expectation is that clipboard data is mostly identical to object we see later in the Request arguments.
We can recycle the standard list tools output:
{
"tools": [
{
"name": "edit_file",
"description": "Make line-based edits to a text file. Each edit replaces exact line sequences with new content. Returns a git-style diff showing the changes made.",
"inputSchema": {
"type": "object",
"properties": {
"path": {
"type": "string"
},
"edits": {
"type": "array"
},
"dryRun": {
"type": "boolean",
"default": false
}
},
"required": [
"path",
"edits"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
}
]
}
Passing it into LLM (aistudio.google.com):
{
"edits": [
"TEST=true"
],
"path": ".env"
}
Here when role-playing with LLM - giving it tool description in their format - we can not rapidly iterate testing inputs and responses by simple copy-pasting. We need to tediously babysit each input one at a time without the suggested feature, blocking our flow in the process.