Always present "Run as Task" checkbox is confusing

[cliffhall]

Inspector Version

• 0.20.0

Describe the bug
The "Run as Task" button is always available on the Tools Tab. But if a tool that cannot be run as a task has this checkbox checked when you run it, you get the error:

MCP error -32602: MCP error -32602: Invalid task creation result: [
  {
    "expected": "object",
    "code": "invalid_type",
    "path": [
      "task"
    ],
    "message": "Invalid input: expected object, received undefined"
  }
]

This is confusing, because the availability of the "Run as Task" checkbox would indicate to a user that this tool could be run as a task.

To Reproduce
Steps to reproduce the behavior:

1. Run the Everything server npx @modelcontextprotocol/server-everything@latest streamableHttp
2. Run the Inspector: npx @modelcontextprotocol/inspector@latest
3. Click Connect
4. Click List Tools
5. Click "Echo" tool in list
6. Enter "Hello" in text to echo field
7. Check "Run as Task"
8. See Tool Result: Error status
9. See JSON Error message below status

Expected behavior

• "Run as Task" should be hidden for tools whose execution.taskSupport setting is forbidden.
• "Run as Task" should shown, enabled, and unchecked for tools whose execution.taskSupport setting is optional.
• "Run as Task" should shown, disabled, and checked for tools whose execution.taskSupport setting is required.

Screenshots
If a tool that cannot be run as a task has this checkbox checked when you run it, you get the following error state:

Environment (please complete the following information):
Any browser

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]

Additional context
Add any other context about the problem here.

Version Consideration

Inspector V2 is under development to address architectural and UX improvements. During this time, V1 contributions should focus on bug fixes and MCP spec compliance. See CONTRIBUTING.md for more details.