Skip to main content
Glama
Sign In

Chessigma

by com.chessigma
OverviewDiscussionsAdmin

Review Online Game

review_online_game
Read-onlyIdempotent

Turn the link of a public Chess.com live game or a Lichess game into a chessigma.com link that imports the game and opens a move-by-move review, computed by Stockfish in the user's browser. Nothing is fetched when this tool runs: the game is read from Chess.com or Lichess only when the user opens the link. Chess.com daily (correspondence) games are not supported; ask for the PGN instead.

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": {
      "url": "<url>"
    },
    "name": "review_online_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA Chess.com live game link or a Lichess game link.

Output Schema

NameRequiredDescriptionDefault
noteYes
platformYes
reviewUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that nothing is fetched at invocation time and that Chess.com/Lichess is read only when the user opens the link, plus that Stockfish runs client-side. These are non-obvious deferred-side-effect semantics the readOnlyHint/idempotentHint annotations cannot express. It omits failure behavior for invalid or non-public links.

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?

Three sentences, zero waste: the core transformation is front-loaded, then the deferred-fetch behavior, then the unsupported-case caveat. Every sentence earns its place and none repeats schema or annotation content.

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

Completeness5/5

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

For a one-parameter, read-only link-generator with an output schema covering the return, the description supplies everything an agent needs: accepted inputs, unsupported inputs, when external fetching happens, and where the review is computed.

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 is 100% and the single url parameter is already documented in the schema. The description's only added semantic is the daily-game exclusion and the public/live constraint, which is modest incremental value over the structured field, so the baseline 3 applies.

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 verb+resource+output: converts a public Chess.com live or Lichess game link into a chessigma.com review link. The transformation target and the computing engine (Stockfish in the browser) are explicit, so an agent can distinguish it from PGN-based siblings like analyze_game.

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

Usage Guidelines4/5

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

Clearly scopes usage to public live/correspondence-supported game links and explicitly excludes Chess.com daily games, redirecting to 'ask for the PGN instead'. It stops short of naming the sibling tool (e.g. analyze_game) that should handle that PGN path, so the routing is implied rather than spelled out.

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

All Chessigma toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources