Crawlora MCP

chesscom_player_stats

Read-only

Get published player statistics for one Chess.com username. The service calls Chess.com’s documented Published-Data API serially. This independent service is not affiliated with Chess.com; do not use results for AI training or dataset creation.

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": {
      "username": "<username>"
    },
    "name": "chesscom_player_stats"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes	Required source username.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 13, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely useful behavior: the upstream API is called serially (implying latency and no parallel hammering), it is a third-party unaffiliated service, and results carry a usage restriction. It stops short of describing error behavior for nonexistent or private usernames.

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?

Three sentences, front-loaded with the action, with no wasted wording. The final disclaimer is slightly boilerplate but is directly relevant to how an agent may use the results.

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?

With an output schema present, return-value explanation is unnecessary, and a single-parameter read-only tool needs little more. The description covers scope, upstream behavior, and usage restrictions, leaving only edge-case behavior (invalid user, missing stats) undocumented.

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?

Only one parameter exists and schema coverage is 100%, so the schema fully documents it. The description reinforces the single-username scope but adds no format or validation details beyond that, which is the expected baseline for a one-param tool.

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 ('Get published player statistics') scoped to a single Chess.com username, which is more precise than the bare tool name. It does not, however, distinguish itself from close siblings such as chesscom_player_profile or chesscom_player_games that an agent might confuse it with.

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 only guidance is the scope constraint 'one Chess.com username'. There is no statement of when to prefer this over profile or per-game siblings, no prerequisites, and no exclusions. The agent must infer usage from the tool name alone.

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

All Crawlora MCP tools Inspect

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

Need Help?