Skip to main content
Glama
Sign In
Chess MCP Server

Chess MCP Server

by fritzprix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

waitForNextTurn

Pause the chess game until the opponent has made their move, guaranteeing the agent acts only when it's its turn. Waits up to 30 seconds for the turn to become available.

Instructions

Blocks until it is the Agent's turn (or User's turn via Agent proxy). Waits up to 30 seconds for the opponent to 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": {
      "game_id": "<game_id>"
    },
    "name": "waitForNextTurn"
  }
}

Input Schema

NameRequiredDescriptionDefault
game_idYesThe ID of the active game.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.12
    • addedInput schema / properties / game_id / description
      Added value: +"The ID of the active game."
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does reveal the blocking nature and timeout. However, it doesn't state what happens when the 30-second wait expires, whether it can be polled repeatedly, or what information it returns. The 'User's turn via Agent proxy' phrasing adds ambiguity rather than clarity.

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?

The description is two short sentences, front-loads the core blocking behavior, and includes the critical timeout detail. Every phrase contributes meaning, with no redundancy or filler.

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?

For a simple one-parameter tool, the description covers the main purpose and timeout. However, the lack of an output schema and the absence of any statement about timeout behavior or return value leaves a notable gap. The ambiguity around 'User's turn via Agent proxy' also reduces completeness.

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?

The only parameter, game_id, is fully described in the schema with 100% coverage. The description does not add any extra semantic detail about how game_id is used beyond the schema, so the baseline score of 3 is appropriate.

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?

The description clearly states the tool's purpose: it blocks until the Agent's turn, with a 30-second wait for the opponent. The verb 'blocks' and the resource 'turn' make the operation understandable, and it is distinct from siblings like finishTurn or joinGame, though it doesn't explicitly reference them.

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

Usage Guidelines3/5

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

The description implies this should be used when waiting for an opponent after your turn, and mentions the 30-second timeout. However, it gives no explicit guidance about when to use it versus alternatives, nor what to do if the timeout elapses. Usage context is only implied, not stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools