Skip to main content
Glama

Read a battle invite

get_battle_invite
Read-onlyIdempotent

Shows who is at the table, the open places on each side and whether the battle has begun. Side indexes start at 0. Use before join_battle. Requires mcp:read.

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": {
      "invite": "<invite>"
    },
    "name": "get_battle_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviteYesThe invite token in the last path segment of the Praetorium join link.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description adds value beyond them: the mcp:read authorization requirement and the 0-based side index convention needed to interpret the result. It stops short of describing error behavior for invalid or expired invites.

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?

Three short sentences, front-loaded with what is returned, then usage, then prerequisite. Every sentence carries information, though the side-index note is slightly displaced since it describes output rather than the call itself.

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 usefully enumerates the returned facts (occupants, open places, started flag) so an agent knows what it will get. Combined with the annotated read-only profile and full schema coverage, an agent has enough to call it correctly; only failure modes are unaddressed.

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%, with the invite token, llm_model and conversation_id all documented in-schema. The description adds nothing about the parameters themselves; the 'side indexes start at 0' note concerns output interpretation rather than input meaning, so the baseline 3 applies.

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 states the specific content returned: who is at the table, the open places per side, and whether the battle has begun. It is clearly a read/preview operation on an invite, though it never explicitly ties itself to the invite token input or names the resource as 'battle invite'.

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?

'Use before join_battle' gives an explicit sequencing rule and names the sibling it precedes, and 'Requires mcp:read' states a prerequisite. It does not state when not to use it or what to do if the invite is already consumed/joined, but the core guidance is present.

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