Crawlora MCP

chesscom_player_live_games

Read-only

Get the source live-game archive selected by base time and increment. 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>",
      "base_time": "<base_time>",
      "increment": "<increment>"
    },
    "name": "chesscom_player_live_games"
  }
}

Input Schema

Name	Required	Description
`username`	Yes	Required source username.
`base_time`	Yes	Required source base time.
`increment`	Yes	Required source increment.

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

B3.1/5.0

Behavior4/5

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

Annotations already cover read-only and open-world, and the description adds genuinely useful behavior beyond them: upstream calls are made serially to Chess.com's Published-Data API, implying latency/throughput characteristics, plus an affiliation disclaimer and a data-use restriction. It does not, however, discuss failure modes when the upstream service is unavailable.

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 short sentences with no padding, and the functional statement leads. The legal and API-mechanics sentences are secondary but each carries information, so nothing is wasteful.

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

Completeness3/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 not be explained, but the description still leaves the core question unanswered: what a "live-game archive" contains (ongoing games? latest archive?) and how it differs from the sibling live_games_base_time tool. For a tool with a genuinely confusing scope, that is a meaningful gap.

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 all three required parameters (username, base_time, increment) are already documented in the schema, and the description only echoes "base time and increment". No format, accepted values, or semantics are added beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get the source live-game archive selected by base time and increment" names a verb and a resource, but "source live-game archive" is ambiguous — it never states plainly that it returns a player's currently/live games for a given time control. The sibling chesscom_player_live_games_base_time is not differentiated, so an agent cannot tell the two apart from the text.

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?

There is no when-to-use guidance and no named alternative among the many sibling game tools (chesscom_player_games, chesscom_player_game_archives, chesscom_player_live_games_base_time). The only directive is a licensing prohibition ("do not use results for AI training"), not selection guidance.

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?