MCP Gateway exposes 8 tools with basic schemas and descriptions, but falls short of production quality. Tool names lack consistent verb-noun structure (e.g., 'virtual-tool list' vs 'list_virtual_tools'). Descriptions are present but generic (10-50 chars for most tools), providing minimal context for LLM selection. Input schemas are visible and typed, but parameter descriptions are sparse or missing entirely. No output schemas documented. Error handling is absent, no recovery guidance, no categorization of retryable vs fatal errors. Security considerations (permission gates, audit trails) are not evident in tool definitions. Composition is reasonable (tools are single-purpose), but chaining support is unclear due to missing output documentation.

• Rename tools to verb_noun convention: 'list_virtual_tools', 'create_virtual_tool', 'show_virtual_tool', 'update_virtual_tool', 'delete_virtual_tool', 'test_virtual_tool', 'validate_virtual_tool', 'set_tool_cache_flags'.
• Expand descriptions to 50-200 chars. Example: 'List all virtual tools with their current status and metadata. Call this first to discover available tools before showing details or testing.' Include when to use, what it returns, and dependencies.
• Document output schemas for all tools. Example for 'list_virtual_tools': {type: 'object', properties: {tools: {type: 'array', items: {type: 'object', properties: {name, description, status, created_at}}}, total: {type: 'integer'}}}.
• Add detailed parameter descriptions with format/constraint hints. Example: 'config: Path to a JSON file defining the virtual tool plan. Must contain {name, description, steps: [{action, params}]}. See /docs/plan-schema.json for full schema.'
• Add error handling and recovery guidance. For 'delete_virtual_tool': 'This is destructive and cannot be undone. If deletion fails, check that no active agents are using this tool. Error codes: 404 (tool not found), 409 (in use by agent), 500 (database error, retry after 30s).' For 'validate_virtual_tool': 'Returns validation errors with line numbers and field paths. Example: {valid: false, errors: [{path: 'steps[0].params.timeout', message: 'must be a positive integer'}]}'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry