Skip to main content
Glama

Chessar.io

surrender

Give up your army.

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": {
      "world": "<world>"
    },
    "name": "surrender"
  }
}

Input Schema

NameRequiredDescriptionDefault
worldYesWorld id, see the worlds tool (e.g. 10s)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Give up" implies an irreversible, destructive act, but nothing states whether it can be undone, what happens to the army or match afterward, or what the result looks like — critical gaps for a forfeit-style operation.

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

Conciseness3/5

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

Four words with zero padding and the action front-loaded, so nothing is wasted. However, the brevity comes at the cost of under-specification rather than being genuinely crisp.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, no-annotation, no-output-schema game action, the definition is far too thin. An agent cannot predict consequences, reversibility, or the outcome of the call from this description alone.

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?

There is a single required parameter and schema description coverage is 100%, including an enum and a pointer to the worlds tool. The description adds nothing about the world parameter, but the schema already does the work, so the baseline of 3 applies.

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

Purpose3/5

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

"Give up your army" names a verb and an in-game resource, so the general intent is legible. But it never says what surrendering mechanically does — resign the game, delete units, forfeit a match — which leaves it only loosely distinguishable from siblings like hibernate or respawn.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no preconditions, and no mention of any alternative action. The agent must infer entirely from the game context whether this is the right tool for its situation.

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