Skip to main content
Glama

Chessar.io

move

Make a move.

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>",
      "pieceId": "<pieceId>",
      "to": "<to>",
      "capture": "<capture>"
    },
    "name": "move"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure and delivers nothing. It does not state that this is a mutating action, whether it requires the caller's turn, what happens when the target square is occupied (the `capture` parameter hints at a capture flow that is never explained), or what errors/validation occur.

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

Conciseness2/5

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

The single sentence is short but wastes its only words on restating the name, so there is nothing front-loaded for the agent to act on. Brevity here reflects under-specification rather than efficient packing of information.

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

Completeness1/5

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

For a four-required-parameter mutation tool with a nested object, a nullable special-case parameter, no annotations, no output schema, and only 25% schema documentation, the description is completely inadequate. It leaves the agent unable to form a correct invocation on its own.

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

Parameters1/5

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

Schema description coverage is only 25% (only `world` is documented), and four parameters are required including a nested `to` object and an oddly typed nullable `capture` id. The description adds zero meaning to any of these — it never explains pieceId, coordinates, or the capture semantics that make the call non-obvious.

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

Purpose2/5

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

"Make a move." merely restates the tool name in sentence form; it names no resource, no board/game context, and gives no verb detail beyond the ambiguous word "move". An agent cannot tell from the description whether this commits a game action, relocates a piece, or changes a world setting, nor how it differs from siblings like moves, place, or join.

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

Usage Guidelines1/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 mention of prerequisites such as turn order or legality, and no reference to any alternative tool. The agent is left to infer everything from the name and the sibling list, which the guidelines explicitly say is not sufficient.

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