Crawlora MCP

chesscom_tournament_round

Read-only

Get one round in a public Chess.com tournament. 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": {
      "slug": "<slug>",
      "round": "<round>"
    },
    "name": "chesscom_tournament_round"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Required source slug.
`round`	Yes	Required source round.

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

Behavior3/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 that calls go serially against Chess.com's Published-Data API, which hints at latency/rate behavior, plus a non-affiliation and no-AI-training notice — useful context but mostly legal boilerplate rather than tool behavior (e.g. errors, missing rounds, pagination).

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

Conciseness3/5

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

The purpose is front-loaded in one clean sentence, but two of the three sentences are disclaimer/legal text that does not help an agent select or invoke the tool and repeats on every call.

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 and annotations cover the read-only profile, so the essentials are present. What is missing is the relationship to the sibling round-group tool and any note on behavior for nonexistent slugs or rounds, which matters for a thin two-parameter lookup.

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 both required parameters (slug, round) are already documented in the schema. The description adds no format, example, or constraint for either parameter, 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 ('Get one round in a public Chess.com tournament'), which is more precise than the bare name. It does not, however, distinguish this from the close sibling chesscom_tournament_round_group or explain how a 'round' relates to a tournament.

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 explicit when-to-use guidance, no mention of when not to use it, and no reference to alternatives such as chesscom_tournament or chesscom_tournament_round_group. The only scoping hint is the word 'public', which an agent must interpret on its own.

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?