Skip to main content
Glama

SportStatsAPI

Find teams

find_teams
Read-only

Find teams by name, with their ids, country, venue and leagues.

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

Input Schema

NameRequiredDescriptionDefault
langNolanguage of team, league and country names: de, es, it or fr (default English)
nameYespart of the team name, e.g. 'Bayern'
limitNomax teams (default 20, max 100)
sportYessport (see list_sports)
league_idNoonly teams of this league

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / league_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds the returned field set, which is useful, but says nothing about the default page size, the 100-team cap, or what happens on an empty match set, all of which matter for a search tool.

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 short sentence with no filler, and the search input is front-loaded ahead of the returned fields. It is efficient but so terse that there is no structured separation between what is searched and what is returned.

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 five parameters, two of them required, and no output schema, the description usefully enumerates the returned fields so the agent knows what it gets back. What remains missing is the find-vs-get distinction against get_team and any note on result limits, which keeps it from a 5.

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 description coverage is 100%, so every parameter including lang, limit and league_id is already documented in the schema, making 3 the baseline. The description contributes only the mention of 'name' and the output fields; it adds no syntax or format hints beyond the schema, and 'leagues' is not clearly linked to the league_id filter.

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 states a specific verb and resource ('Find teams by name') and even enumerates what comes back ('ids, country, venue and leagues'), which lets an agent picture the result. It falls short of 5 because it never distinguishes this lookup from the sibling get_team or find_leagues, so the agent must infer when name-search beats a direct fetch.

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?

Usage is only implied: the phrase 'by name' and the required name/sport pair suggest a search-style lookup rather than a fetch-by-id. There is no explicit when-to-use, no statement of when to prefer get_team, and no note that sport is mandatory, leaving routing between the two team tools to inference.

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