You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|**Automation**| N/A | Ideal for CI/CD pipelines, batch processing, and integration with coding assistants |
468
468
|**Learning MCP**| Rich visual interface helps new users understand server capabilities | Simplified commands for focused learning of specific endpoints |
469
469
470
+
## Tool Input Validation Guidelines
471
+
472
+
When implementing or modifying tool input parameter handling in the Inspector:
473
+
474
+
-**Omit optional fields with empty values** - When processing form inputs, omit empty strings or null values for optional parameters, UNLESS the field has an explicit default value in the schema that matches the current value
475
+
-**Preserve explicit default values** - If a field schema contains an explicit default (e.g., `default: null`), and the current value matches that default, include it in the request. This is a meaningful value the tool expects
476
+
-**Always include required fields** - Preserve required field values even when empty, allowing the MCP server to validate and return appropriate error messages
477
+
-**Defer deep validation to the server** - Implement basic field presence checking in the Inspector client, but rely on the MCP server for parameter validation according to its schema
478
+
479
+
These guidelines maintain clean parameter passing and proper separation of concerns between the Inspector client and MCP servers.
480
+
470
481
## License
471
482
472
483
This project is licensed under the MIT License—see the [LICENSE](LICENSE) file for details.
0 commit comments