APIbase exposes 35 tools across weather, crypto, polymarket, and travel domains. While tool names follow verb_noun conventions and descriptions are present, the actual parameter schemas and output structures are NOT visible in the provided source code. The file src/mcp/tool-definitions.ts is referenced but not shown, making it impossible to verify JSON Schema definitions, parameter type constraints, or output documentation. Only tool names and high-level descriptions are visible. This forces conservative scoring: per the hard rules, tools without visible schemas score 0 on schema dimension. Additionally, descriptions are generic and brief (30-40 chars typical), offering minimal guidance on WHEN to use each tool vs. alternatives, parameter constraints, or expected output structure. The polymarket.place_order tool is marked DESTRUCTIVE but no evidence of confirmation/dry-run patterns. No visible error recovery guidance. Composition is reasonable (35 separate, single-purpose tools), but without schema inspection, quality cannot be certified.

• Export and document src/mcp/tool-definitions.ts with complete JSON Schema for all 35 tools. Include input parameter types (string, number, enum), constraints (min/max, regex pattern, allowed values), and descriptions for each parameter.
• Expand tool descriptions from 30-55 chars to 150-250 chars. Explain WHEN to use this tool vs related ones, what location/identifier formats are accepted, what units/currencies are returned, and any prerequisites (e.g. 'Requires API key' if applicable).
• Add explicit error recovery guidance to each tool description. E.g. 'If location not found, try weather.geocode(location_name) first. Returns errors like INVALID_COORDINATES (fix lat/lon range) or RATE_LIMITED (retry after 60s)'.
• Document output schema for each tool: list the fields returned, their types, and when fields may be absent. E.g. 'Returns {temperature: number (Celsius), humidity: 0-100, forecast: [date, high_temp, low_temp, condition]}.'
• Add pagination parameters (limit, offset/page) to list tools (crypto.trending, polymarket.search, sabre.search_flights) and document them. Cap results at 50 items by default with option to request next page.
• For polymarket.place_order (DESTRUCTIVE), add a dry_run flag or explicit confirmation step in the description. E.g. 'Set dry_run=true to preview order without placing. Requires explicit dry_run=false to execute.'
• Add idempotency guidance where applicable. E.g. 'polymarket.place_order accepts an optional order_id_token to prevent duplicate orders on retry. Use UUID or client-provided ID.'

Inferred effective spec: 2025-06-18+.

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