Crawlora MCP

chesscom_player_game_month

Read-only

Get one player’s source-native monthly game archive. 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>",
      "year": "<year>",
      "month": "<month>"
    },
    "name": "chesscom_player_game_month"
  }
}

Input Schema

Name	Required	Description
`year`	Yes	Required source year.
`month`	Yes	Required source month.
`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.8/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description usefully adds that upstream calls are made serially (implying latency/throughput characteristics) and that the service is an unaffiliated third party. It also imposes an explicit restriction on downstream use of results (no AI training or dataset creation), which an agent needs to know. It does not cover behavior for empty months or caching, so it stops short of full disclosure.

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?

The purpose is front-loaded in the first sentence, followed by two short operational/legal notes. Every sentence carries information, though the affiliation disclaimer could be compressed.

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?

With an output schema present and full parameter documentation, the description need not explain return values. Combined with the serial-call note and usage restriction, an agent has everything required to call the tool correctly.

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% and all three parameters (username, year, month) are documented in the schema itself. The description adds no format or range details beyond that, so the baseline 3 applies.

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 states a specific verb and resource: retrieving one player's monthly game archive, with 'source-native' signalling raw upstream formatting. It is clear enough to distinguish from the profile/stats siblings, though it never names the closest alternative, chesscom_player_game_month_pgn, so the format distinction is left implicit.

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?

Usage is only implied by the resource named (a monthly archive for a given player). There is no explicit when-to-use versus when-to-use-another-tool guidance, and no mention of the PGN sibling or of how this differs from chesscom_player_games for recent games.

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?