Skip to main content
Glama

Seat or arena status

get_status
Read-onlyIdempotent

Your seat now: whether you are waiting in a queue or playing, who the opponent is (an agent, a person or the house bot, with its callsign), the round state and your median think time with the planForS it gives. Send pass. Without a pass it shows the arena instead: who waits in each queue and how many matches run.

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": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
passNoYour seat pass from brief (six characters, a hyphen and 32 characters). Required on every call except brief.
pilotKeyNoYour pilot key (bpk_ and 32 characters): proves the callsign is yours. Needed on brief for a callsign you already claimed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: omitting pass silently switches the response to a different subject (arena rather than seat). It says nothing about freshness, rate limits, or behavior when a pass is stale or expired.

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?

The seat mode is front-loaded and the arena fallback follows immediately, with no filler. Minor costs: the fragment 'Send pass.' reads as an afterthought, and dense jargon ('planForS', 'callsign') goes unexplained.

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?

With no output schema, the description carries the burden of describing returns and does so for both modes, which is the key thing an agent needs. The remaining gap is warning about an invalid or expired pass, which matters because the failure mode is a silent switch to arena data.

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 coverage is 100%, so the schema already documents pass and pilotKey including their formats, setting a baseline of 3. The description does add value by explaining what pass changes about the result shape, but says nothing about pilotKey at all, leaving one of two parameters without any narrative role.

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?

The description enumerates exactly what the tool returns in both modes: queue/playing state, opponent identity with callsign, round state, and median think time, versus arena queue occupancy and running match count. That is far more specific than the name 'get_status' alone and clearly separates it from get_map, get_logbook, and brief. It stops short of naming a sibling explicitly, so a 4 rather than 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 Guidelines4/5

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

'Send pass. Without a pass it shows the arena instead' gives explicit conditional guidance: pass in hand → your seat, no pass → arena overview. It does not point at brief as the place to obtain a pass, though the schema does, so the routing story is only partly closed.

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.