Skip to main content
Glama

SportStatsAPI

Find leagues

find_leagues
Read-only

Find leagues (competitions) of a sport and their ids, optionally by name or country (also matches official_name, the competition's official or Wikidata name where known). Works without an account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sport": "<sport>"
    },
    "name": "find_leagues"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNolanguage of team, league and country names: de, es, it or fr (default English)
queryNotext the league or country name must contain, e.g. 'Premier League' or 'Germany'
sportYessport: soccer, basketball, baseball, hockey, tennis, handball, volleyball, american-football, cricket, rugby (union), rugby-league, esports or table-tennis
futureNoonly leagues with upcoming matches

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sport / description
      Previous value: -"sport: soccer, basketball, baseball, hockey, tennis, handball, volleyball, american-football, cricket, rugby (union), rugby-league or esports"New value: +"sport: soccer, basketball, baseball, hockey, tennis, handball, volleyball, american-football, cricket, rugby (union), rugby-league, esports or table-tennis"
  2. Changed1 schema field changed
    • changedInput schema / properties / sport / description
      Previous value: -"sport: soccer, basketball, baseball, hockey, tennis, handball, volleyball, american-football, cricket, rugby (union) or rugby-league"New value: +"sport: soccer, basketball, baseball, hockey, tennis, handball, volleyball, american-football, cricket, rugby (union), rugby-league or esports"
  3. Changed1 schema field changed
    • changedInput schema / properties / sport / description
      Previous value: -"sport: soccer, basketball, baseball, hockey, tennis, handball, volleyball, american-football or cricket"New value: +"sport: soccer, basketball, baseball, hockey, tennis, handball, volleyball, american-football, cricket, rugby (union) or rugby-league"
  4. Changed1 schema field changed
    • changedInput schema / properties / sport / description
      Previous value: -"sport: soccer, basketball, baseball, hockey, tennis, handball, volleyball or american-football"New value: +"sport: soccer, basketball, baseball, hockey, tennis, handball, volleyball, american-football or cricket"
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely new behavioral context: no account is required, and the name/country filter also matches a competition's official_name or Wikidata name. It does not mention result limits or pagination behavior, which is the remaining gap for a search endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the core action and the optional filters come first. The nested parenthetical about official_name is slightly dense but earns its place by clarifying matching behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With full schema coverage, read-only annotations and no output schema, the description covers what the tool does, what the filters match, and the auth-free nature. Only pagination or result-size expectations are unstated, a minor omission for a lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning beyond the schema by explaining that the query filter matches official_name/Wikidata names in addition to league and country names. The sport, lang and future parameters are left to the schema, which already documents them fully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb plus resource ("Find leagues") and clarifies that leagues are competitions and that ids are returned, which is the key output. It does not explicitly contrast itself with sibling lookups such as find_teams or get_league_facts, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It conveys implied usage — search by sport, optionally narrowed by name or country, and usable without an account. There is no explicit when-to-use/when-not guidance or named alternative for retrieving richer league data (e.g. league facts or fixtures), leaving that inference to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources