Skip to main content
Glama

Football Data

Get Competition Standings

get_competition_standings
Read-onlyIdempotent

League table / standings for a competition season, Premier League, Championship, Primera División/La Liga, Serie A, Bundesliga, Ligue 1, Eredivisie, Primeira Liga, Brasileirão, Copa Libertadores, UEFA Champions League, European Championship, or the World Cup. Returns total / home / away tables.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "competition": "PL"
    },
    "name": "get_competition_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoSeason start year (optional, defaults current)
matchdayNoStandings as of a specific matchday (optional)
competitionYesCompetition code

Output Schema

NameRequiredDescriptionDefault
standingsYes
competitionYesCompetition name or code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "competition": "PL"
      +  },
      +  {
      +    "competition": "PD",
      +    "matchday": 10,
      +    "season": 2024
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "competition": {
      +      "description": "Competition name or code",
      +      "type": "string"
      +    },
      +    "standings": {
      +      "items": {
      +        "properties": {
      +          "group": {
      +            "description": "Group name if applicable",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "stage": {
      +            "description": "Stage name (e.g., FINAL_STANDINGS)",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "table": {
      +            "items": {
      +              "properties": {
      +                "draw": {
      +                  "description": "Games drawn",
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "form": {
      +                  "description": "Recent form (W/D/L sequence)",
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "ga": {
      +                  "description": "Goals against",
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "gd": {
      +                  "description": "Goal difference",
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "gf": {
      +                  "description": "Goals for",
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "lost": {
      +                  "description": "Games lost",
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "played": {
      +                  "description": "Games played",
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "points": {
      +                  "description": "Total points",
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "position": {
      +                  "description": "Table position",
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "team": {
      +                  "description": "Team name",
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "team_id": {
      +                  "description": "Team ID",
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "won": {
      +                  "description": "Games won",
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                }
      +              },
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "type": {
      +            "description": "Standings type (TOTAL, HOME, AWAY)",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "competition",
      +    "standings"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds that total, home, and away tables are returned, which is useful behavioral context beyond annotations, but it does not describe other traits such as rate limits or permissions.

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?

The description is two sentences and front-loads the core purpose. The long competition enumeration is somewhat verbose but earns its place because the schema has no enum for competition codes, making supported competitions relevant to callers.

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?

The tool is simple with three parameters, an output schema exists, and annotations cover safety. The description lists supported competitions and return table variants, which is largely complete, though it omits guidance on finding competition codes and when to prefer this tool over sibling match-listing tools.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all three parameters. The description does not add syntax or format detail beyond what the schema provides, though it lists competition names that may help interpret the competition code parameter. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the tool returns league tables/standings for a competition season and lists supported competitions. It is specific about verb and resource, but does not explicitly differentiate itself from sibling tools such as get_competition_matches or list_competitions.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no mention of alternatives, and no prerequisites or exclusions. The listing of competitions implies context but does not tell an agent when to choose this tool over related siblings.

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.