Skip to main content
Glama
fritzprix

Chess MCP Server

by fritzprix
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

createGame

Start a new chess game session by specifying opponent type (computer, agent, or human), color, and AI difficulty. Returns a Game ID and instructions for play.

Instructions

Initializes a new chess game session. Returns the Game ID and instructions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesOpponent type. 'computer': Play against AI (No UI). 'agent': Play against another Agent (No UI). 'human': Play against Human (Returns UI).
colorNoYour color. 'white' moves first. If 'black', the opponent will move first.white
difficultyNoAI Difficulty Level (1-10), if type is 'computer'.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.1.17
    • changedInput schema / properties / color / description
      Previous value: -"Your color. 'white' moves first. If 'black', computer will move first."New value: +"Your color. 'white' moves first. If 'black', the opponent will move first."
  2. Changed7 schema fields changedv0.1.12
    • removedInput schema / $defs
      Removed value: -{
-  "GameConfig": {
-    "properties": {
-      "color": {
-        "default": "white",
-        "description": "Your color. 'white' moves first. If 'black', computer will move first.",
-        "enum": [
-          "white",
-          "black"
-        ],
-        "title": "Color",
-        "type": "string"
-      },
-      "difficulty": {
-        "default": 5,
-        "description": "AI Difficulty Level (1-10), if type is 'computer'.",
-        "maximum": 10,
-        "minimum": 1,
-        "title": "Difficulty",
-        "type": "integer"
-      },
-      "showUi": {
-        "default": false,
-        "description": "If true, returns an interactive HTML board in waitForNextTurn. Required for human players.",
-        "title": "Showui",
-        "type": "boolean"
-      },
-      "type": {
-        "description": "Play against 'computer' (AI) or 'agent' (another tool/human)",
-        "enum": [
-          "computer",
-          "agent"
-        ],
-        "title": "Type",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type"
-    ],
-    "title": "GameConfig",
-    "type": "object"
-  }
-}
    • addedInput schema / properties / color
      Added value: +{
+  "default": "white",
+  "description": "Your color. 'white' moves first. If 'black', computer will move first.",
+  "enum": [
+    "white",
+    "black"
+  ],
+  "title": "Color",
+  "type": "string"
+}
    • removedInput schema / properties / config
      Removed value: -{
-  "$ref": "#/$defs/GameConfig"
-}
    • addedInput schema / properties / difficulty
      Added value: +{
+  "default": 5,
+  "description": "AI Difficulty Level (1-10), if type is 'computer'.",
+  "maximum": 10,
+  "minimum": 1,
+  "title": "Difficulty",
+  "type": "integer"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Opponent type. 'computer': Play against AI (No UI). 'agent': Play against another Agent (No UI). 'human': Play against Human (Returns UI).",
+  "enum": [
+    "computer",
+    "agent",
+    "human"
+  ],
+  "title": "Type",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "config"
-]New value: +[
+  "type"
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "createGameOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of disclosing side effects and behavior. It does state the core side effect (initializes a session) and that it returns a Game ID and instructions, but it omits any context about permissions, session lifecycle, whether repeated calls create multiple sessions, or type-dependent outcomes. For a state-changing tool, this is thin 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?

The description consists of two short, front-loaded sentences: the first states the core action, the second the return value. There is no filler, and every sentence adds information. It is concise without sacrificing the essentials.

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?

The tool has no output schema and no annotations, so the description's 'Returns the Game ID and instructions' is the only return guidance. It does not specify the shape of the return value, how the Game ID should be used with sibling tools, or the fact that the return differs by opponent type (e.g., human returns UI). It is minimally adequate but leaves gaps for a stateful, multi-tool workflow.

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 coverage for parameters is 100%, so the baseline is 3 even though the description adds no parameter-specific meaning. The description does not mention type, color, or difficulty, leaving all parameter semantics to the input schema, which is adequate.

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?

The description opens with 'Initializes a new chess game session,' which names a specific action (initializes) and resource (chess game session), and adds that it returns the Game ID and instructions. This clearly distinguishes it from sibling tools like waitForNextTurn or joinGame by focusing on session creation.

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 verb 'initializes' implies that this tool is for starting a new game rather than joining (joinGame) or progressing an existing one, but no explicit when-to-use or when-not-to-use guidance is provided. The description does not name alternatives or conditions, leaving the agent to infer usage from the tool name and sibling list.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fritzprix/chess-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server