Crawlora MCP

chesscom_player_clubs

Read-only

Get a player’s public club memberships. 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_clubs"
  }
}

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real context beyond that — the backing service calls Chess.com's Published-Data API serially, which signals latency/throughput behavior, plus licensing and affiliation caveats. It omits error behavior (unknown user, private clubs) and whether an empty list is a valid result.

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 operative sentence is front-loaded and clear, but two of the three sentences are boilerplate disclaimers (non-affiliation, no AI training) that do not help an agent select or invoke the tool. They pad the definition without adding selection value.

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 one required parameter fully documented and an output schema present, return values need no explanation, and the description covers scope, data source, and safety context adequately. The remaining gap is minor: no note on what happens for a nonexistent or private-profile username.

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% and the single parameter is documented as the required source username, so the schema carries the burden. The description only reinforces that it is a player username; it adds no format, case-sensitivity, or resolution rules. 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?

"Get a player's public club memberships" gives a specific verb (get) and resource (club memberships) scoped to a player, which is distinguishable from a club-centric tool like chesscom_club_members. It stops short of explicitly naming that sibling, so the differentiation is inferable rather than stated.

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, no mention of alternatives such as chesscom_club_members (club → members) versus this tool (player → clubs), and no preconditions. The only implied usage is the direction of the lookup, which the agent must derive from the name and description.

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?