Skip to main content
Glama
Sign In
Chess MCP Server

Chess MCP Server

by fritzprix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

finishTurn

Submit a chess move in UCI format to an active game and get the updated board state or a precise error. Optionally claim checkmate or win with the move.

Instructions

Submits a move and returns the updated state or a precise failure.

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>",
      "move": "<move>"
    },
    "name": "finishTurn"
  }
}

Input Schema

NameRequiredDescriptionDefault
moveYesThe move in UCI format (e.g., 'e2e4').
game_idYesThe ID of the active game.
claim_winNoSet to true if you are claiming Checkmate or Win with this move.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.12
    • addedInput schema / properties / claim_win / description
      Added value: +"Set to true if you are claiming Checkmate or Win with this move."
    • addedInput schema / properties / game_id / description
      Added value: +"The ID of the active game."
    • addedInput schema / properties / move / description
      Added value: +"The move in UCI format (e.g., 'e2e4')."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "finishTurnOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden of explaining behavior. It does disclose the return behavior ('returns the updated state or a precise failure'), which is useful, but it does not describe side effects, turn ownership requirements, or the meaning of the claim_win option. This is a reasonable partial disclosure.

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?

A single tight sentence front-loads the action and then gives the expected result. Every phrase contributes, with no repetition of the title or schema fields.

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

Completeness4/5

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

For a simple move-submission tool with fully documented parameters, the description plus schema is nearly complete. It would benefit from a brief note on when it is valid to call (e.g., only during the player's turn), but the lack of an output schema is mitigated by stating the return behavior.

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 description coverage is 100%, so all three parameters already have meaningful schema descriptions (e.g., UCI format, claim_win semantics). The tool description adds little about the parameters, but it does not need to compensate for missing schema coverage.

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

Purpose5/5

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

States a specific action ('Submits a move') and its result, clearly distinguishing it from sibling tools like waitForNextTurn, createGame, and joinGame. No ambiguity about what resource/operation this covers.

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 context of submitting a move is implicit given the name and UCI-formatted move parameter, but the description never explicitly says when to call it or when to prefer a sibling such as waitForNextTurn. No alternatives or exclusions are named, so the agent must infer usage from the verb and parameter names.

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