Skip to main content
Glama

Play both sides of a battle

play_both_battle_sides
Destructive

Fills the open places in a draft with practice seats the signed-in player can control. Use create_battle with bothSides when starting a fresh draft. 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": {
      "token": "<token>"
    },
    "name": "play_both_battle_sides"
  }
}

Input Schema

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

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description usefully adds an authorization requirement ('Requires mcp:manage') plus the side effect of adding controllable seats. However, it never explains why the operation is destructive — whether filled seats can be removed later, or what happens to existing seats — which is the key unknown for a destructive 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?

Two sentences, zero waste: the action is front-loaded, followed immediately by the alternative and the auth requirement. Every clause earns its place.

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?

Covers purpose, alternative, and authorization for a destructive mutation with no output schema. It omits reversibility, the effect on existing players, and any indication of what is returned, which leaves meaningful gaps for a destructive operation.

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 67%, and the three parameters (token, llm_model, conversation_id) are analytics/identity metadata already described in the schema. The description adds no parameter meaning, which is acceptable at this coverage level but not value-adding.

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 and resource: fills the open places in a draft with practice seats the signed-in player controls. It also names the sibling path (create_battle with bothSides) for fresh drafts, so the agent can tell the two apart. The only gap is that 'draft' and 'practice seats' are not defined, but the action is concrete.

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?

Explicitly routes the fresh-draft case to create_battle with bothSides, implying this tool is for an existing draft with open seats. There is no explicit when-not guidance (e.g., behavior on a full draft or a finished battle), but the primary alternative is clearly named.

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