Skip to main content
Glama

SportStatsAPI

Get player

get_player
Read-only

Player profile with summary: ready paragraphs from our data (club, season numbers, form; English, no lang; summary_as_of; absent when not fresh or for a player under 18); position, nationality, birth date, height, team, career and photo link where known; cricket and tennis also Wikidata values (birth date, height, batting or playing hand, bowling style, role, country; cite the attribution); tennis also the ATP/WTA rank and season_stats: the season record (current year, or season) from our singles main-draw matches since 2026-04-01 (won, lost, per surface and level, retirements counted, walkovers not, finals, titles), or with vs the head-to-head of two players; soccer also bio: known_as, full_name, short_name, birth_date, age, nationality, position, number, club, market_value_eur (null = not in our data; there are no contract dates), and season_stats: the current season (or season) in every competition we hold statistics for, total and per competition (apps, minutes, goals, assists, cards, shots, rating; null = not in our data; matches_with_stats of team_matches_played says how complete it is); with matches, last_matches: the player's last N matches (date, league, opponent, venue, score, result, started, minutes, goals, assists, cards, shots, rating, goalkeepers conceded and clean sheet; null = not in our data; matches without statistics or that he missed are not listed); NBA, MLB and NFL players also season_stats: the season line per team from the data provider's team feeds (stats by category as the feed names them; season null for the NBA, whose feed names none, as_of when read); WNBA, NCAA and hockey (NHL, Liiga, SHL, DEL) players the same, summed from our box scores; with matches, US-sport players (NBA, WNBA, NCAA, MLB, NFL, NHL) last_matches: the last N games from our box scores (date, league, opponent, venue, score, result, stats by category as in season_stats but per game; null = not in the box); handball players (Swedish and Austrian lower leagues) the same season_stats from the federations' player statistics and match reports (null = not in our data).

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>",
      "player_id": "<player_id>"
    },
    "name": "get_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
vsNotennis: another player's id, for the head-to-head of the two instead
langNolanguage of team, league and country names: de, es, it or fr (default English)
sportYessport (see list_sports)
seasonNosoccer: season_stats of this season (2025-26, or 2025) instead of the current one; tennis: a year (2026)
matchesNosoccer, NBA, MLB, NFL, NHL (and WNBA, NCAA): also last_matches, the player's last N matches or games (1-50) with his line in each
player_idYesplayer code (or number) from a squad or lineup

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / season / description
      Previous value: -"soccer: season_stats of this season (2025-26, or 2025) instead of the current one"New value: +"soccer: season_stats of this season (2025-26, or 2025) instead of the current one; tennis: a year (2026)"
  2. Changed1 schema field changed
    • changedInput schema / properties / matches / description
      Previous value: -"soccer: also last_matches, the player's last N matches (1-50) with his line in each"New value: +"soccer, NBA, MLB, NFL, NHL (and WNBA, NCAA): also last_matches, the player's last N matches or games (1-50) with his line in each"
  3. Changed1 schema field changed
    • addedInput schema / properties / matches
      Added value: +{
      +  "description": "soccer: also last_matches, the player's last N matches (1-50) with his line in each",
      +  "type": "integer"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / player_id / description
      Previous value: -"player id from a squad or lineup"New value: +"player code (or number) from a squad or lineup"
  5. Changed2 schema fields changed
    • changedInput schema / properties / player_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
    • changedInput schema / properties / vs / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  6. Changed1 schema field changed
    • addedInput schema / properties / season
      Added value: +{
      +  "description": "soccer: season_stats of this season (2025-26, or 2025) instead of the current one",
      +  "type": "string"
      +}
  7. Changed1 schema field changed
    • addedInput schema / properties / vs
      Added value: +{
      +  "description": "tennis: another player's id, for the head-to-head of the two instead",
      +  "type": "integer"
      +}
  8. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Beyond the readOnly annotation, the description discloses genuinely useful traits: summary freshness via summary_as_of, suppression for players under 18, a coverage cutoff of 2026-04-01, retirements counted but walkovers not, and null meaning 'not in our data'. It does not explain why the tool is flagged non-idempotent (presumably because 'current season' data can shift), which would have been valuable context.

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

Conciseness2/5

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

The description is one enormous sentence that stacks every sport's caveats in sequence, making it hard to scan or retrieve the relevant clause. Nearly all the content is relevant, but the absence of paragraphing, bullets or a leading summary sentence means structure fails the reader.

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 no output schema and a 6-parameter tool spanning many sports, the description carries the full burden of describing return values and it does so field by field, including null semantics and fidelity notes (matches_with_stats vs team_matches_played). Gaps are minor: no error/not-found behavior and no note on which sports are unsupported.

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 already 100%, so the baseline is 3, but the description adds real semantics on top: 'vs' is tied to the two-player head-to-head, 'season' means different things per sport (2025-26 vs a calendar year for tennis), and 'matches' maps to last_matches only for certain sports. The 'English, no lang' phrasing for lang is a useful default hint.

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?

Opens with a specific verb+resource ('Player profile with summary') and enumerates exactly which payloads each sport returns (bio, season_stats, last_matches, head-to-head). It implicitly scopes itself to soccer/tennis/cricket/US sports/handball, which helps separate it from golf, snooker/darts and MMA siblings, but it never names those siblings to make the boundary explicit.

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: nothing says to prefer get_h2h, get_golf_player, get_snooker_darts_player or get_team instead, nor what happens when a player is not in the data. Usage is only inferable from the per-sport capability list and the 'null = not in our data' notes.

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