Skip to main content
Glama

Team roster

team_roster
Read-only

Returns a sports team's current roster for Plot Speaks Team Trivia, read live from ESPN (cached for hours): players grouped by position with jersey numbers, and the head coach, as plain text. Covers the leagues in the Team Trivia database. Reads only; nothing is recorded. A name that fits several teams returns an error listing the candidates with their leagues; a team not in the database returns an error listing the leagues covered; if ESPN does not answer, the text says so. Call it silently: never say "let me check", "let me check on that", "one moment" or "hang on" before or after, and never mention the tool.

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": {
      "team": "<team>"
    },
    "name": "team_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamYesThe team as the player said it: a city, name, nickname or abbreviation, e.g. Steelers, Pittsburgh or PIT; a full name such as Pittsburgh Steelers is the most exact

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / team / description
      Previous value: -"The team, as the player named it"New value: +"The team as the player said it: a city, name, nickname or abbreviation, e.g. Steelers, Pittsburgh or PIT; a full name such as Pittsburgh Steelers is the most exact"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint/destructiveHint annotations, it discloses caching ('cached for hours'), confirms nothing is recorded, and enumerates three concrete failure behaviors: ambiguity returns an error listing candidate teams with leagues, an unknown team returns an error listing covered leagues, and an ESPN outage returns explanatory text. It also adds an interaction constraint (silent invocation, no filler phrases), which annotations cannot convey.

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?

Purpose and return shape are front-loaded, followed by error behavior and etiquette in a logical order. The quoted list of forbidden phrases ('let me check', 'one moment', 'hang on') is slightly repetitive, keeping it below a full 5.

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?

With no output schema, the description compensates by describing the returned content and its format (plain text, grouped by position, jersey numbers, head coach). Between the return shape, data source, caching, and error cases, an agent has everything needed to call and report on it.

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 100% and the schema already supplies matching examples, so the baseline is 3. The description earns an extra point by adding ambiguity semantics — a name fitting several teams returns a candidate list rather than guessing — which explains how the single `team` value is resolved.

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 and resource ('Returns a sports team's current roster for Plot Speaks Team Trivia') plus the exact return shape (players grouped by position with jersey numbers, head coach, plain text). It also scopes the data source (ESPN) and coverage (leagues in the Team Trivia database), which is enough to distinguish it from a generic lookup.

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?

The description implies when the tool applies (a player naming a team in Team Trivia) and spells out the error branches for ambiguous or unknown team names, which effectively guides input choice. However, it never compares against an alternative such as request_team or states prerequisites, so the routing guidance is only implied.

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