Skip to main content
Glama

Get Arena Attendance

get_arena_attendance
Read-only

Retrieve your arena's attendance records, ticket prices, and gate revenue, newest first. Filter by team ID and paginate results to review recent home-game financial performance.

Instructions

Info about your own arena. Attendance, prices and gate revenue, newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
team_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds the useful ordering trait ('newest first'), but says nothing about pagination behavior despite limit/offset parameters, nor about how much history is available.

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?

Two short sentences, front-loaded with the resource and followed by the returned fields and ordering. No wasted words, though the terseness contributes to the missing parameter and sibling guidance.

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

Completeness2/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 values need not be described, but with 0% parameter coverage and an unaddressed sibling (get_team_arena) the definition leaves real gaps for a three-parameter tool. The agent cannot tell how to page or how this differs from the related arena 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?

Schema description coverage is 0% across three parameters, so the description must compensate and does not. It never explains what team_id means (own team vs any team), nor what limit and offset control, leaving the agent to guess at paging semantics.

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 resource (arena attendance) and enumerates the data returned: attendance, prices, gate revenue, plus ordering ('newest first'). It does not distinguish itself from the sibling get_team_arena, which likely covers overlapping arena data, so it falls short of a 5.

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?

'Info about your own arena' implies the scope is the caller's team, but there is no explicit when-to-use guidance and no mention of when to prefer get_team_arena or get_team_economy instead. The agent must infer the choice from names alone.

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