Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

lichess_cloud_eval

Read-only

Returns the cached cloud evaluation for one X-FEN position. Optional multiPv and source chess variant values select the requested evaluation; use the official export for bulk data.

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": {
      "fen": "<fen>"
    },
    "name": "lichess_cloud_eval"
  }
}

Input Schema

NameRequiredDescriptionDefault
fenYesRequired X-FEN position for the source cloud-evaluation lookup.
multiPvNoOptional number of principal variations requested from the source; the source default is 1.
variantNoOptional source variant; defaults to standard.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the meaningful detail that results are *cached*, implying possible staleness or absence, but it does not say what the response looks like when no cloud eval exists for the position - the most likely failure mode for this call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the return behavior and followed by the parameter role and the bulk-data redirect. Every clause carries information; minor redundancy in the repeated phrase 'source ... evaluation' is the only drag.

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?

An output schema exists, so return values need no explanation, and the parameter surface is fully documented in the schema. What remains thin is the no-result behavior for a cached lookup, which an agent would benefit from knowing before calling.

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%, so the schema already documents fen, multiPv and variant, including defaults. The description only echoes that multiPv and variant 'select the requested evaluation', adding no format, range, or X-FEN syntax detail beyond the structured fields - baseline 3.

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?

States a specific verb and resource: 'Returns the cached cloud evaluation for one X-FEN position.' The scope ('one', 'cached') is precise enough to separate it from a general engine or bulk export, though it does not name any sibling tool such as lichess_tablebase as a contrasting option.

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?

It gives one explicit exclusion ('use the official export for bulk data'), which tells the agent this is a single-position lookup rather than a batch call. However, no guidance is offered on when a tablebase or puzzle tool would be a better choice, and nothing is said about what to do when no cached evaluation exists.

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

All Crawlora MCP 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