Skip to main content
Glama

Football Data

Football Data Get Team

football_data_get_team
Read-onlyIdempotent

Team detail by ID, current squad, coach, competitions, venue.

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

Input Schema

NameRequiredDescriptionDefault
team_idYesfootball-data.org numeric team ID

Output Schema

NameRequiredDescriptionDefault
idYesTeam ID
tlaNoThree-letter acronym
nameYesTeam full name
coachNoCoach name
crestNoTeam crest/logo URL
squadYes
venueNoStadium/venue name
colorsNoClub colors description
addressNoTeam address
countryNoCountry name
foundedNoYear founded
websiteNoOfficial website URL
short_nameNoTeam short name
coach_nationalityNoCoach nationality
running_competitionsYesList of competition names team is currently in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and side-effect profile is fully covered structurally. The description's additive value is telling the agent what fields come back (squad, coach, competitions, venue), which helps it decide whether this call answers the question. It says nothing about error behavior for unknown IDs, rate limits, or freshness of squad data.

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?

One compact line with the resource front-loaded and zero filler. The comma-fragment style is dense but readable, and nothing in it is redundant with structured fields in a wasteful way.

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 one required parameter fully documented, an output schema present, and rich annotations, the description only needs to convey what the tool returns — which it does by listing squad, coach, competitions, venue. The main residual gap is guidance on sourcing the team_id and behavior on invalid IDs, which for a simple read tool is a minor omission.

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?

There is a single required parameter with 100% schema description coverage ('football-data.org numeric team ID'), so the schema already does the semantic work. 'By ID' in the description merely echoes the parameter without adding format, range, validity, or discovery guidance (e.g., how to obtain a team_id). Baseline 3 applies.

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 fragment 'Team detail by ID' names a specific resource and lookup key, and the remaining items (squad, coach, competitions, venue) enumerate what the detail payload contains. It is clearly distinguishable from get_team_matches, which concerns fixtures rather than the team entity itself. It falls short of 5 only because the telegraphic noun-phrase style leaves the action ('retrieve/fetch') implicit.

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 when-to-use or when-not-to-use statement, and no alternative is named or contrasted, even though get_team_matches and get_competition_standings sit adjacent. An agent must infer from the noun list alone that this is the profile/enrichment call rather than the results call.

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.