Skip to main content
Glama
Sign In
Lichess MCP

Lichess MCP

by karayaman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

handle_draw_board_game

Accept or decline draw offers in Lichess chess games to manage game outcomes and resolve stalemate situations.

Instructions

Handle draw offers for a board game

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": {
      "gameId": "<gameId>"
    },
    "name": "handle_draw_board_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameIdYesThe game ID
acceptNoWhether to accept or decline the draw offer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('handle draw offers') but lacks critical details: whether this is a read-only or mutating operation, what permissions are required, if it affects game state permanently, or what happens after acceptance/declination. The description is too vague for safe agent use.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core purpose and avoids unnecessary elaboration, making it easy to parse quickly.

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 tool with no annotations and no output schema, the description is inadequate. It doesn't explain the behavioral implications of accepting/declining a draw (e.g., game outcome, score changes), error conditions, or return values. Given the complexity of game state mutations, more context is needed for reliable agent use.

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 the schema fully documents both parameters (gameId and accept). The description adds no additional parameter context beyond implying the tool relates to draw offers, which is already inferred from the tool name. This meets the baseline for high schema coverage.

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 verb ('handle') and resource ('draw offers for a board game'), making the purpose understandable. It doesn't explicitly differentiate from siblings like 'resign_board_game' or 'claim_victory', but the focus on draw offers is specific enough to avoid confusion with other game-ending actions.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active draw offer), timing considerations, or how it differs from other game-resolution tools like 'resign_board_game' or 'claim_victory' in the sibling list.

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