Enhance tool call input

[isaacwasserman]

Is your feature request related to a problem? Please describe.
Tools with complex object input schemas can be difficult to work with because we're only given a <textarea/> in the UI.

Describe the solution you'd like
Provide a JSON editor component, rather than a textarea for object inputs. This component could be pre-populated with the fields of the input schema.

Describe alternatives you've considered

1. Alternatively, object properties could be expanded into multiple inputs up to a reasonable depth.
2. At the very least, the textarea could have a default value that provides the JSON structure required by the schema.

[olaservo]

I added a draft approach here for the maintainers to review, let me know what you think: #136

[WAY29]

+1, need more complex tool call input

[olaservo]

I updated my original PR to add a JSON editing component in order to resolve conflicts and took it out of draft: #136

Still working on providing an updated version of the Everything server to help test more complex inputs.

[olaservo]

A few enhancements were merged this AM. Please take a look at the latest from main and let me know if you have any suggestions for further improvements!

[WAY29]

A few enhancements were merged this AM. Please take a look at the latest from main and let me know if you have any suggestions for further improvements!

hi, maybe something like array is not corret. here is an object-array example:

{
  "type": "object",
  "properties": {
    "test": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "key": {
            "type": "string",
            "default": "aaa"
          }
        }
      }
    }
  }
}

In mcp inspector it is a string input box:

Expect the following effects:

[olaservo]

A couple updates on related changes:

@kshern was awesome and added more robust array handling in this PR: #157

There are still some open issues I noticed when it comes to editing object fields, and there's also this open issue with handling fields that are supposed to be integers: #154

I have an open PR here tp address both of those, and since the tool input logic is starting to get pretty complicated I also started adding automated tests: #159