Skip to main content
Glama

List teams

list_teams
Read-onlyIdempotent

Use when you need team abbreviations, or to see all 32 active NHL teams with city, conference, division, and arena. Excludes historical franchises (ATL, ARI). Cheapest tool at 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 nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl, ahl, ushl.
divisionNoFilter by division
conferenceNoFilter by conference

Output Schema

NameRequiredDescriptionDefault
countYes
teamsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / teams / items / properties / arena / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / league / description
      Previous value: -"League. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl."New value: +"League. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl, ahl, ushl."
    • changedInput schema / properties / league / enum
      Previous value: -[
      -  "nhl",
      -  "pwhl",
      -  "ohl",
      -  "whl",
      -  "qmjhl",
      -  "echl"
      -]New value: +[
      +  "nhl",
      +  "pwhl",
      +  "ohl",
      +  "whl",
      +  "qmjhl",
      +  "echl",
      +  "ahl",
      +  "ushl"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / league / description
      Previous value: -"League. Defaults to nhl. One of: nhl, pwhl."New value: +"League. Defaults to nhl. One of: nhl, pwhl, ohl, whl, qmjhl, echl."
    • changedInput schema / properties / league / enum
      Previous value: -[
      -  "nhl",
      -  "pwhl"
      -]New value: +[
      +  "nhl",
      +  "pwhl",
      +  "ohl",
      +  "whl",
      +  "qmjhl",
      +  "echl"
      +]
  4. Changed1 schema field changed
    • addedInput schema / properties / league
      Added value: +{
      +  "description": "League. Defaults to nhl. One of: nhl, pwhl.",
      +  "enum": [
      +    "nhl",
      +    "pwhl"
      +  ],
      +  "type": "string"
      +}
  5. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description's added value is the credit cost and the data-scope note about excluded franchises, which is genuinely useful. However, it frames the result as 'all 32 active NHL teams,' which understates that the tool can be scoped to eight different leagues — a behavioral fact the agent needs.

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?

Three short clauses, front-loaded with the use case, followed by the output shape and the exclusion. Nothing is padded and the cost note is one compact phrase.

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

Completeness3/5

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

An output schema exists, so the return values need not be explained, and the safety profile comes from annotations. The remaining gap is real, though: for a tool with three optional filter parameters spanning multiple leagues, the description never acknowledges filtering or non-NHL leagues, leaving the agent with an inaccurate mental model.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the league, division, and conference parameters are already fully documented with enums. Rather than supplementing that, the description says 'all 32 active NHL teams,' which implies a fixed NHL-only, unfiltered result and contradicts the presence of a league enum spanning PWHL, OHL, WHL, QMJHL, ECHL, AHL, and USHL.

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?

States a specific verb plus resource (list teams) and enumerates the payload fields (city, conference, division, arena). It also names the primary use case — retrieving team abbreviations — and rules out historical franchises, so an agent can distinguish it cleanly from stats/detail siblings.

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?

Opens with an explicit 'Use when you need team abbreviations' trigger and states an exclusion (historical franchises ATL, ARI). It does not name a competing sibling or describe when to prefer get_team_stats or get_standings instead, so it stops short of full routing guidance.

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.