Patchbay exposes 4 gateway meta-tools for MCP server lifecycle management. All tools lack input schemas entirely (schema score = 0 for all). Descriptions are present but minimal (10-20 chars), failing the 20-char floor for description scoring. No parameter documentation visible. Tools are namespaced correctly (patchbay__*) but lack the structured definitions required for LLM-safe invocation. This is a gateway/infrastructure tool, not a user-facing agent tool, which explains the minimal schema investment, but MCP spec requires formal tool registration with schemas regardless of purpose.

• Add JSON Schema inputSchema to all 4 tools. For add_jack, define: {type: 'object', properties: {jack_name: {type: 'string', description: '...'}, config: {...}}, required: ['jack_name']}. See src-tauri/src/gateway/tools.rs for namespacing logic.
• Expand tool descriptions to 50 - 150 chars. Example: 'patchbay__add_jack: Register a new MCP server (jack) with Patchbay. Provide the jack name and connection config. Returns the jack ID and initial status.' This tells LLMs when to call it and what to expect.
• Document every parameter with type, format, and constraints. E.g., jack_name: 'string, 1 - 40 chars, alphanumeric + dash/underscore, no __ separator (validated by config::validate).'
• Define output schemas for each tool. E.g., list_jacks returns {jacks: [{name: string, status: 'running'|'stopped', pid?: number}], total: number}. This enables tool chaining and LLM planning.
• Add error handling guidance in descriptions. E.g., 'If jack_name already exists, returns error code JACK_EXISTS. Try list_jacks to see configured jacks, or use a different name.'

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

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