The SportQuanta MCP catalog is generated from the canonical public OpenAPI document. It currently contains 152 tools, exactly one per eligible REST method/path pair, with an empty product exclusion list. Infrastructure and private endpoints are filtered before catalog generation: health, readiness, metrics, internal, admin, webhook-ingress, and service-to-service routes are never offered to a model. The server also does not provide a generic call_api(method, path) escape hatch.

​
Naming

Each tool name is the operation’s stable OpenAPI operationId converted to snake case. For example: tools/list is the runtime authority for the complete name list and schemas. The API Reference is the human-readable operation catalog; every non-infrastructure operation shown there has one corresponding tool.

​
Inputs

Path and query parameters appear as top-level tool arguments with the same names and required/optional status as OpenAPI. A JSON request body, when a public write operation is introduced, appears under body. Schemas reject unknown fields. Credentials and internal headers are never tool arguments. Example:
That call becomes:

​
Tool families

The catalog covers the customer operations in the canonical REST reference:
  • token and tenant context;
  • sports, leagues, bookmaker coverage, markets, and prop catalogs;
  • schedules, games/matches, live state, teams, players, venues, lineups, rotations, rosters, injuries, standings, and leaderboards;
  • current, opening, closing, fair, best-price, historical, movement, CLV, divergence, settlement, and player-prop data;
  • baseball batting, pitching, bullpen, pitch-type, zone, plate-discipline, first-inning, NRFI, matchup, recap, and play-by-play detail;
  • basketball defense, DVP, tracking, play-by-play, shot chart, and play-type detail;
  • soccer events, match details, statistics, commentary, momentum, lineups, missing players, form, head-to-head, squad history, and call-ups;
  • Korean Proto/Toto fixtures, rounds, and prices.
Aliases that are independently documented REST routes remain independent tools because coverage is defined by method/path, not by handler implementation. Optional analytics-proxy routes and WebSocket channels are separate interfaces, not generated MCP tools. See Sports Analysis API and WebSocket Streaming.

​
Results and errors

Successful JSON REST responses are returned both as text content and as structuredContent. The result metadata includes the upstream HTTP status and request ID when available. REST failures return isError: true. Safe fields such as API error code, HTTP status, user-facing message, operation ID, and request ID are retained; arbitrary upstream details and infrastructure errors are not copied through. Authentication, scopes, plan access, quota, rate limiting, and billing always use the existing REST API behavior.