io.github.DanielTomaro13/sportsdata-mcp

List every tool group across all providers, which are currently enabled, and each provider's auth requirements (env-var names + required/optional). On a fresh install (no groups enabled) this is the only functional tool, so the model can guide the user to enable what they want in sportsdata-mcp.yaml.

Discover tools by capability — the unit of cross-provider comparison. Given a slug like 'sport.event_markets', returns every enabled tool exposing it across providers. Pass no argument for the full capability → tools map.

List all registered MCP resources (capability map, dispatcher catalogues, reference data).

How this server has performed for you THIS session: per-tool call counts, error rates, error codes, latency buckets, and how often a tool succeeded but returned nothing. Useful when a tool seems to be misbehaving — a 100% error rate with code AUTH_REQUIRED means a missing key, while a high `empty` count on a working tool usually means the upstream has no data for what was asked, not that the call is wrong. This is read from local counters. Nothing here has been sent anywhere.

Report whether an answer from this server was useful. Call this when a tool gave a wrong, empty or misleading answer — especially if the response shape did not match its description, which is the failure mode the maintainers most need to hear about. Recorded locally. It is only ever transmitted if the operator has explicitly enabled sharing (SPORTSDATA_TELEMETRY=1 plus a configured endpoint), and `note` is sent verbatim, so do not put anything private in it.