Skip to main content
Glama

SportAPI Football Data

Player match stats

get_player_match_stats
Read-only

Per-match statistics and totals for a player, found by name and team id.

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": {
      "name": "<name>",
      "team_id": "<team_id>"
    },
    "name": "get_player_match_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPlayer name as shown in squads or lineups
team_idYes
shirt_numberNoHelps when two players share a name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), but the description adds nothing about scope: which competitions or season the matches come from, how many matches are returned, ordering, or pagination. For an open-world stats lookup, the scope of returned data is the key behavioral unknown and it is left unstated.

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. It is efficient, though its brevity is part of why other dimensions are under-served.

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

Completeness2/5

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

With no output schema and an open-world data source, the description should at least say what scope of matches is covered (season, competition) and roughly what a stat record contains. Neither is present, leaving the agent unable to predict the response.

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 coverage is 67% and the one undocumented parameter, team_id, gets meaning from the description's 'found by name and team id' phrasing, which reveals it is part of the lookup key rather than a filter. shirt_number is explained in the schema itself (disambiguation), so the description does not need to repeat it.

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?

States a specific resource (per-match statistics and totals for a player) and the lookup keys (name and team id). This reasonably distinguishes it from get_player (profile-level) and get_top_players (aggregate leaders), though it does not name those siblings explicitly.

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?

The phrase 'found by name and team id' implies the call pattern, but there is no guidance on when to prefer this over get_player or get_top_players, nor any mention of prerequisites such as needing to resolve team_id first via find_teams.

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