Skip to main content
Glama

Chessar.io

place

Place a recruit next to your King.

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>",
      "type": "<type>",
      "to": "<to>"
    },
    "name": "place"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description bears the full behavioral burden. It does disclose one positional rule ("next to your King"), which is useful, but says nothing about required permissions, turn order, whether the placement is reversible, or what happens when the target square is invalid.

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?

A single front-loaded sentence with no filler, but it is terse to the point of under-specification for a tool with a nested object and three required parameters. Brevity here costs more than it saves.

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 mutation-style game action with a nested coordinate object, two enums, no annotations, and no output schema, one sentence is far short of what an agent needs to call it correctly. Key legality and failure behavior are entirely absent.

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

Parameters2/5

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

Schema description coverage is only 33% (only "world" is documented), so the description must compensate and does not. The nested "to" coordinates and their ±30000 range are unexplained, and the "type" enum is obscured by the word "recruit" rather than aligned with the piece-type values.

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?

The description names a verb and object ("Place a recruit"), but it conflicts with the schema, which lets the caller pick any piece type from the enum Q/R/B/N/P rather than only a "recruit." The added constraint "next to your King" is not represented in the schema at all, and nothing distinguishes this from the sibling "move" tool, so the agent must guess at the real scope.

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 prerequisites (turn, game state, legality), and no mention of alternatives such as "move", "join", or "respawn" despite clear sibling overlap. Only an implicit game-action context is conveyed.

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