Skip to main content
Glama

Get Team Roster

get_team_roster
Read-only

Retrieve a team's complete roster by team ID, including player names, ages, DMI, and game shape; skill values are included only for your own team.

Instructions

Give the complete roster of a team. For your own team, you also get the skill values, otherwise you'll get only the public information (name, age, DMI, game shape)

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_id": "<team_id>"
    },
    "name": "get_team_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and delivers real value: it discloses that output contents vary by team ownership (skill values vs. public-only fields like name, age, DMI, game shape). It stops short of stating error behavior for invalid team_ids or whether the roster includes staff/loaned players.

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 short sentences with zero filler, and the ownership-dependent behavior is stated immediately after the core purpose. Every clause carries information.

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?

An output schema exists, so the description needn't enumerate return values, and it is sufficient for an agent to call the tool correctly. The only gap is the absence of any hint about identifier format or how ownership is determined, which is minor for a single-parameter read.

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 0% for the single team_id parameter, so the description needs to compensate. It confirms team_id identifies "a team" and implies the notion of "your own team," but adds no format, type, or sourcing guidance for the identifier.

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?

States a specific verb and resource ("Give the complete roster of a team") that clearly identifies the operation. It does not explicitly distinguish itself from near-name siblings such as get_national_team_roster or scout_team, so the agent must infer the difference from the word "team" alone.

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 context is implied through the conditional "For your own team... otherwise...", which tells the agent what data is available per case, but there is no explicit when-to-use guidance, no prerequisite for obtaining a team_id, and no named alternative for related queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.