Skip to main content
Glama

Next report

next_report
Read-onlyIdempotent

Wait for the next report (up to waitSeconds, default 8, at most 20) and return it. Send pass and after (the seq of the last report you saw). A report holds your mech (position, headings, speed, heat, health, weapons), contacts, the enemy when in sight, an estimate when not, alerts since the last report, the round state and the orders now in force. Returns report null on timeout. act does this and more in one call; prefer act.

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

Input Schema

NameRequiredDescriptionDefault
passNoYour seat pass from brief (six characters, a hyphen and 32 characters). Required on every call except brief.
afterNoThe seq of the last report you saw. Default 0.
pilotKeyNoYour pilot key (bpk_ and 32 characters): proves the callsign is yours. Needed on brief for a callsign you already claimed.
waitSecondsNoHow long to wait for the next report, in seconds. Default 8, at most 20; 50 when no person is in the room.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / waitSeconds / description
      Previous value: -"How long to wait for the next report, in seconds. Default 8, at most 20."New value: +"How long to wait for the next report, in seconds. Default 8, at most 20; 50 when no person is in the room."
    • changedInput schema / properties / waitSeconds / maximum
      Previous value: -20New value: +50
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds real behavior beyond them: the wait semantics (up to waitSeconds), the timeout outcome ('Returns report null on timeout'), and the full shape of what is returned. Minor tension: the description says 'at most 20' for waitSeconds while the schema allows a maximum of 50, which an agent must reconcile from the schema alone.

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?

Front-loaded with the action and the wait bound, then the parameter hint, then the return shape, then the sibling preference — every sentence carries information. Slightly dense prose (one long enumeration sentence for report contents) but no filler.

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?

No output schema exists, so the description properly compensates by enumerating what a report contains and what happens on timeout. The one unresolved gap is the waitSeconds ceiling conflict (20 in prose vs 50 in schema) and no note on how repeated calls with a stale 'after' behave.

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 100%, so pass, after, pilotKey and waitSeconds are already documented in structured data; baseline 3 applies. The description adds only a light gloss on 'after' ('the seq of the last report you saw') and repeats the waitSeconds default, and says nothing about pilotKey.

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

Purpose5/5

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

States a specific verb and resource ('Wait for the next report ... and return it') and immediately scopes what a report is: mech state, contacts, enemy, alerts, round state and orders. It also names the sibling it overlaps with ('act does this and more in one call; prefer act'), so the agent can differentiate without opening another schema.

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?

Gives an explicit preference rule against the main alternative ('act does this and more in one call; prefer act'), which is strong routing guidance. It also tells the agent what to send ('pass and after (the seq of the last report you saw)'), but never states the positive condition under which this tool beats act (e.g., pure polling when you have nothing to submit), leaving the agent to infer it.

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.