Skip to main content
Glama

List teams

list_teams
Read-onlyIdempotent

Use to find club ids and abbreviations for a season (default: the latest), with each club's colour, second colour, a readable text colour on it and logo. Every other tool takes a club as an id, abbreviation or name. Pass league for MLS (mls), La Liga (laliga), Serie A (seriea), the Bundesliga (bundesliga), Ligue 1 (ligue1), the Champions League (ucl), the EFL Championship (championship), the NWSL (nwsl), Liga MX (ligamx), the Europa League (uel), the Conference League (uecl), the Eredivisie (eredivisie), the Primeira Liga (primeira), the Scottish Premiership (scotland), Brazil's Serie A (brazil) or Argentina's Liga Profesional (argentina); default: the Premier League. Costs 1 credit.

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": "list_teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.
seasonNoSeason by the year it starts: 2025 = 2025-26. MLS, the NWSL, Liga MX, Brazil and Argentina: the calendar year. Default: the latest.

Output Schema

NameRequiredDescriptionDefault
countYes
teamsYes
seasonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds useful context such as the 1-credit cost and the returned club metadata. It does not discuss rate limits or other operational constraints, but with strong annotation coverage this is a solid disclosure.

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?

The key purpose is front-loaded, followed by the usage prerequisite and parameter guidance. The long league enumeration is useful but somewhat verbose because it repeats enum values already present in the schema.

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?

Given the simple two-parameter lookup, the description covers purpose, prerequisites, defaults, cost, and returned club fields. An output schema exists, so the description does not need to explain the response structure further.

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 both parameters are already documented. The description adds human-readable league-code mappings, but it omits the schema's `soccer` enum value and claims the default is the Premier League while the schema says the default is `soccer`, creating a minor semantic conflict.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 club ids and abbreviations for a season, plus each club's colours and logo. It also distinguishes this lookup from every other sibling by explaining that all other tools require a club id, abbreviation, or name.

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

Usage Guidelines5/5

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

It explicitly says to use this tool to obtain club identifiers and notes that every other tool consumes a club as an id, abbreviation, or name, giving clear prerequisite context. It also explains the league selector and defaults, leaving little ambiguity about when and how to call it.

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.