Skip to main content
Glama

SportStatsAPI

Get team

get_team
Read-only

Team profile: country, founded, venue, leagues, logo link; summary (soccer, NBA, NHL, MLB, NFL teams): ready paragraphs from our data (table place and gaps, record, form, home and away, squad leaders, next opponent; English; with lang de, es, it or fr in sold sports and a plan with Insights: the team briefing's most important facts in that language, from our fact templates only, else English; summary_lang says which; not with squad, injuries or season_stats of a US team; summary_as_of; absent when not fresh); rating: its Elo-style rating (rank of of in its league, matches_rated, rated_from, the last 10 changes); next: its next 5 matches in every competition (more: get_matches with team_id; fixture congestion: get_team_briefing). Soccer also coach: the current head coach from Wikidata with appointment date and won/drawn/lost since (record_complete false: our matches start later, at record_from, so say the record covers only that; cite the attribution), and squad_value_eur: the current squad's summed market value over players_with_value of squad_players. Options: squad (the players); soccer: coach (adds previous_coach and previous_club), facts (runs, first since, milestones; Insights feature), season_stats (the current season per league: home/away records, goals, clean sheets, biggest win and defeat, xG over matches_with_xg, home attendance over matches_with_attendance, the team's rank per metric), transfers (the latest 20), honours (titles and runners-up with sources), injuries (players out for coming matches: type, expected_return null = not known; matches_missed a lower bound when matches_missed_complete is false). For an MLB, NBA, WNBA, NHL or NFL team, injuries returns its current injury report and season_stats its season statistics instead of the profile.

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

Input Schema

NameRequiredDescriptionDefault
langNolanguage of team, league and country names: de, es, it or fr (default English)
coachNosoccer: also return coach: the head coach with appointment date, record since, previous coach and previous club
factsNosoccer: also return facts: current runs, runs its last match ended, first since, record, table, next match stakes, player milestones (needs the insights feature)
sportYessport (see list_sports; not tennis)
squadNoalso return the squad (players)
honoursNosoccer: also return honours: titles and runners-up per competition, each with its source (provider: the profile's trophy list, every competition, can lag the latest season; wikipedia: league tables of the last 10 seasons) and disagreements, seasons the sources tell apart: report both, never pick one silently
team_idYesteam code (or number) from find_teams or a match
injuriesNoreturn the team's injury report instead (MLB, NBA, WNBA, NHL, NFL); soccer: added as injuries (players out for its coming matches with type, expected_return, matches_missed); needs the injuries feature
transfersNosoccer: also return the team's latest 20 transfers in and out (more: get_transfers)
season_statsNoreturn the team's current season statistics instead (MLB, NBA, WNBA, NHL, NFL); soccer: added as season_stats (per league, computed from our matches)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / team_id / description
      Previous value: -"team id from find_teams or a match"New value: +"team code (or number) from find_teams or a match"
  2. Changed2 schema fields changed
    • changedInput schema / properties / honours / description
      Previous value: -"soccer: also return honours: titles and runners-up per competition, each with its source (goalserve: the profile's trophy list, every competition, can lag the latest season; wikipedia: league tables of the last 10 seasons) and disagreements, seasons the sources tell apart: report both, never pick one silently"New value: +"soccer: also return honours: titles and runners-up per competition, each with its source (provider: the profile's trophy list, every competition, can lag the latest season; wikipedia: league tables of the last 10 seasons) and disagreements, seasons the sources tell apart: report both, never pick one silently"
    • changedInput schema / properties / team_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / honours
      Added value: +{
      +  "description": "soccer: also return honours: titles and runners-up per competition, each with its source (goalserve: the profile's trophy list, every competition, can lag the latest season; wikipedia: league tables of the last 10 seasons) and disagreements, seasons the sources tell apart: report both, never pick one silently",
      +  "type": "boolean"
      +}
  4. Changed5 schema fields changed
    • addedInput schema / properties / coach
      Added value: +{
      +  "description": "soccer: also return coach: the head coach with appointment date, record since, previous coach and previous club",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / facts
      Added value: +{
      +  "description": "soccer: also return facts: current runs, runs its last match ended, first since, record, table, next match stakes, player milestones (needs the insights feature)",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / injuries / description
      Previous value: -"return the team's injury report instead (MLB, NBA, WNBA, NHL, NFL; needs the injuries feature)"New value: +"return the team's injury report instead (MLB, NBA, WNBA, NHL, NFL); soccer: added as injuries (players out for its coming matches with type, expected_return, matches_missed); needs the injuries feature"
    • changedInput schema / properties / season_stats / description
      Previous value: -"return the team's current season statistics instead (MLB, NBA, WNBA, NHL, NFL)"New value: +"return the team's current season statistics instead (MLB, NBA, WNBA, NHL, NFL); soccer: added as season_stats (per league, computed from our matches)"
    • addedInput schema / properties / transfers
      Added value: +{
      +  "description": "soccer: also return the team's latest 20 transfers in and out (more: get_transfers)",
      +  "type": "boolean"
      +}
  5. Changed2 schema fields changed
    • addedInput schema / properties / injuries
      Added value: +{
      +  "description": "return the team's injury report instead (MLB, NBA, WNBA, NHL, NFL; needs the injuries feature)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / season_stats
      Added value: +{
      +  "description": "return the team's current season statistics instead (MLB, NBA, WNBA, NHL, NFL)",
      +  "type": "boolean"
      +}
  6. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Substantially exceeds the annotations (readOnlyHint, openWorldHint=false, idempotentHint=false). It discloses data provenance (Wikidata coach, provider vs wikipedia trophy sources), freshness handling (summary_as_of, summary absent when not fresh), and explicit incomplete-data caveats (record_complete false → record starts at record_from; matches_missed_complete false → lower bound; expected_return null = unknown). The language-fallback rules for lang and summary_lang are also spelled out, which no annotation or schema field conveys.

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?

A single ~250-word run-on sentence chain joined by semicolons and nested parentheses, with the most important facts buried inside clauses. Much of the parameter text repeats the schema, and the summary/authored-content block is nearly unparseable on first read. It would be far stronger split into a one-line purpose plus short option notes.

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?

For a 10-parameter, no-output-schema tool spanning multiple sports, it covers the hard parts well: data sources, freshness, incomplete-record warnings, cross-sport behavior switches and language fallbacks. Remaining gaps are minor — no indication of the response envelope or how optional sections are keyed, though the option names imply it.

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 100%, so the schema already documents every flag, and much of the description's option text is near-duplicate of the schema descriptions. It does add some meaning beyond the schema — notably flag interactions ('not with squad, injuries or season_stats of a US team') and what soccer coach returns when combined (previous_coach, previous_club) — but that addition is modest against a fully documented schema.

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 enumerates precisely what is returned (profile fields, summary, Elo-style rating, next 5 matches, plus optional coach/squad_value) and names siblings for adjacent needs (get_matches for more fixtures, get_team_briefing for congestion, get_transfers). It is not a crisp one-line purpose statement — the first clause reads as a field list rather than 'retrieves X' — but an agent can still tell it apart from get_player or get_summary from the content alone.

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

Usage Guidelines4/5

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

Each option is annotated with its applicability (coach/facts/season_stats/transfers/honours are soccer-only; injuries/season_stats switch to a different behavior for MLB/NBA/WNBA/NHL/NFL), and explicit alternatives are given for related needs (get_matches with team_id, get_team_briefing, get_transfers). What is missing is any guidance on the base case — when to call get_team at all versus get_player, get_standings or get_summary.

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