Skip to main content
Glama

game_get_messages

Read-onlyIdempotent

[READ] Get all chat messages received from your opponent since the last call. Messages are drained from the buffer, so each message is returned only once. Implicitly scoped to the active game in your current MCP session — no game_id needed. Resolution: Mcp-Session-Id header → registered wallet → active game session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior2/5

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

The description is behaviorally rich on its own terms, disclosing the drain-on-read semantics and the full session-resolution chain (Mcp-Session-Id header → registered wallet → active game session). However, that drain behavior directly conflicts with the supplied idempotentHint=true annotation: repeating the call does not yield the same result, since messages are consumed. That inconsistency is the kind of trait the description raises but the annotations deny, leaving the agent with conflicting signals.

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

Conciseness5/5

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

Three short sentences, front-loaded with the read tag and the core action, then the non-obvious drain rule, then the scoping/resolution detail. No sentence is filler and each adds a distinct fact.

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 parameters and no output schema, the description covers what an agent must know to call it correctly: no ids needed, results are consumed, and scoping is automatic. The only gap is a hint about message shape (sender, timestamp, ordering), which would help the agent parse results without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the schema baseline is 4. The description goes further by explaining why none are needed and by documenting the implicit scoping mechanism, which is meaningful information not expressible in an empty object schema.

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?

The description uses a specific verb and resource ("get all chat messages received from your opponent") and pins the temporal scope ("since the last call"). The "[READ]" prefix and the "received from your opponent" framing clearly separate it from the send-side sibling game_send_message.

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?

It makes the polling contract explicit: messages are drained, each is returned only once, so an agent knows it must call repeatedly and must not expect replay. It also states no game_id is required and how the active game is resolved. What it lacks is any named alternative or a "when not to use" condition (e.g., use game_get_result for outcome data).

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.

Resources