Skip to main content
Glama

SportAPI Football Data

Team

get_team
Read-only

A team by id or slug (e.g. "arsenal") with recent and upcoming matches. Optionally the squad (player slugs) and trophies (each adds one request; the slug form already includes the squad).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
slugNoTeam slug, used when team_id is not given
includeNo
team_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, it discloses a real behavioral cost model — each include entry triggers an additional request — and a non-obvious quirk, that the slug form already includes the squad. It does not describe response format or failure behavior for a bad id/slug, which keeps it below a 5.

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

Conciseness5/5

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

Two tightly packed sentences with no filler; the core resource and payload are front-loaded and the cost caveat follows immediately.

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

Completeness5/5

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

No output schema exists, and the description compensates by stating the returned payload (team, recent and upcoming matches). With annotations covering the safety profile and the includes' cost model explained, an agent has enough to call this correctly.

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 only 33% (only slug is documented), so the description must compensate, and it does: it clarifies the id-or-slug choice and gives the meaning and cost of each include value, something the enum alone does not convey. It still says nothing about team_id's type/constraints or the precedence when both keys are given.

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 names a specific resource (a team) and the lookup keys (id or slug), and states what the response contains (recent and upcoming matches) plus optional squad/trophies. It implicitly separates itself from find_teams by being an exact-identifier lookup, but never says so 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?

Guidance is limited to the optional includes: it explains that each adds one request and that the slug form already carries the squad. There is no statement of when to prefer this over find_teams, nor what happens if neither team_id nor slug is supplied (0 required parameters), leaving selection logic partly inferred.

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