Skip to main content
Glama

Get Team Arena

get_team_arena
Read-only

Retrieves public information about a team's arena, including seats and ticket prices.

Instructions

Public information about a team arena (seats and prices).

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_arena"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes the safe-read profile, so the description's burden is lighter. It does add one useful disclosure beyond the annotations: the data is 'public,' implying no sensitive or private arena details and presumably no elevated permissions. It says nothing about error behavior for an invalid team_id or whether results can be empty.

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 a clarifying parenthetical — no wasted words and the key content (seats, prices) is front and center. The brevity is efficient rather than padded, though it tips into under-specification elsewhere.

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 return-value explanation is not required, and the readOnlyHint covers the safety profile. What remains missing is the meaning of the sole parameter and any routing guidance among the many team-related siblings, which is noticeable but not fatal for a simple one-parameter read tool.

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?

The single required parameter team_id has 0% schema description coverage, so the description is the only place its meaning could be clarified. It never mentions team_id, leaving the agent to assume it is an internal team identifier rather than, say, a name or slug.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (team arena) and the data returned (seats and prices), so the agent knows roughly what to expect. However, the verb is a vague 'information about' and it does not distinguish this from close siblings such as get_team_facilities or get_team, which plausibly overlap.

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

Usage Guidelines2/5

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

There is no guidance on when to call this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer usage purely from the tool name and the parenthetical hint.

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