Skip to main content
Glama

Join a battle from an invite

join_battle

Takes an open place on side 0 or 1 from get_battle_invite. Confirm the host and side with the player before joining. Requires mcp:manage.

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>",
      "side": "<side>"
    },
    "name": "join_battle"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
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.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and the description usefully adds an auth requirement (mcp:manage) plus a human-confirmation step that annotations cannot express. However, it omits what happens on failure (side taken, invite expired, already joined) and does not note that joining can later be undone — relevant given the withdraw_from_event sibling — leaving meaningful behavioral gaps for a mutation.

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, fully front-loaded: the action first, then the prerequisite tool and confirmation step, then the permission requirement. No filler or restated title text.

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?

For a mutation with no output schema, it covers source of input, auth scope, and a safety precondition, which is most of what an agent needs. It stops short of stating the return value (e.g., whether a battle id comes back) or error behavior, which are the remaining unknowns before calling.

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?

At 75% schema coverage the baseline is 3; the description restates the side 0/1 constraint and the invite's origin, both of which the schema already documents. It says nothing about the optional analytics parameters (llm_model, conversation_id), so it adds little beyond structured data.

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?

States a specific verb+resource: taking an open place on side 0 or 1 of a battle, sourced from get_battle_invite. This distinguishes it from sibling joins (join_event, join_group, join_league) by tying it to a battle invite token, though it never explicitly names which sibling covers the non-invite path.

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 a clear prerequisite chain: obtain the invite via get_battle_invite, then confirm host and side with the player before joining. It lacks exclusions, such as what to do if the side is already full or the player is already in the battle, but the when-to-use context is explicit.

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