Critical failure: Tool definitions are inferred from file references only. No explicit tool registration, schemas, or parameter definitions visible in provided source code. Tool names and descriptions appear only in comments/test files, not in actual MCP server implementation. Cannot verify input schemas, output schemas, or parameter types.

• Locate and provide the actual MCP tool registration code (likely in cmd/gateway or internal/mcp). Show explicit tool definitions with names, descriptions, input schemas, and output schemas.
• Expand tool descriptions to 100-200 chars following pattern:tool-description. Example: 'discover_models: Query upstream provider account to list available AI models. Returns model IDs, names, capabilities, and pricing. Call this first to see what models are available before validating credentials.'
• Define input schemas for all parameters. Example for validate_credentials: {type: 'object', properties: {provider_account_id: {type: 'string', description: 'UUID of the upstream provider account'}, credentials: {type: 'object', description: 'Provider-specific credential object'}}, required: ['provider_account_id', 'credentials']}
• Document output schemas. Example for read_usage: {type: 'object', properties: {account_id: {type: 'string'}, usage_tokens: {type: 'integer'}, reset_date: {type: 'string', format: 'date-time'}, remaining_quota: {type: 'integer'}}}
• Add error handling guidance. Example: 'If validate_credentials returns 401, the credentials are invalid, ask the user to verify. If it returns 429, retry after 60 seconds. If 500, the provider service is down, suggest checking provider status page.'