Skip to main content
Glama

Map and weapon facts

get_map
Read-onlyIdempotent

The map facts once: name, size, boundary radius, landmarks (name, kind, position, height) and the numbers that matter (top speed, sight range, lock time, weapons with range, damage, heat and cooldown). The brief holds the same. Weapons, top speed and heat are for the build you field now. Send pass.

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

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

C2.8/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 two useful behavioral notes beyond that: weapon/top-speed/heat values reflect the currently fielded build, and a pass is expected on the call. It says nothing about response shape or whether the data is cached per match.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the phrasing is clipped to the point of ambiguity ('The map facts once', 'Send pass'), and the return-value enumeration dominates while the core action statement is absent. The sentences earn their place content-wise, but the telegraphic style costs clarity.

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?

There is no output schema, so the description carries the burden of describing return values — and its field enumeration (landmarks with name/kind/position/height, weapons with range/damage/heat/cooldown) is the most valuable part of the text. However, it omits the call's auth expectations and any indication of data size or structure, leaving the definition only partially complete for a no-output-schema tool.

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% and both parameters are fully documented in the schema, so the baseline is 3. 'Send pass' loosely reinforces the `pass` parameter, but the description says nothing about `pilotKey` or why both parameters are technically optional despite the auth framing.

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 identifies the resource (map facts: name, size, boundary radius, landmarks, combat numbers) but never states a verb and is written in a compressed, telegraphic style. It partially differentiates from the sibling `brief` by noting 'The brief holds the same,' but an agent has to infer that this is a read of static map data rather than a briefing summary.

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?

'Send pass.' implies an auth requirement but gives no when-to-use guidance, no exclusions, and no explicit pointer to the `brief` alternative beyond the ambiguous 'The brief holds the same.' The agent is left to infer the choice between this tool and `brief` on its own.

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.