Crawlora MCP

chesscom_country

Read-only

Returns only the public country profile metadata (country name and code) from Chess.com's Published-Data API. It does not enumerate players or clubs.

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": {
      "iso": "<iso>"
    },
    "name": "chesscom_country"
  }
}

Input Schema

Name	Required	Description	Default
`iso`	Yes	Required two-character uppercase country code from the source country profile path.

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

A4.2/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 largely covered. The description does add useful context that the payload is public and restricted to name/code, but says nothing about error behavior for unknown codes, rate limits, or caching beyond what the annotations and output schema supply.

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

Conciseness5/5

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

Two short sentences with zero waste; the payload restriction is front-loaded and the scope exclusion follows immediately. Nothing repeats the name or title and no filler is present.

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?

Output schema covers return values and the description need only frame intent, which it does. For a one-parameter lookup with full schema coverage the definition is nearly complete; only failure modes for an invalid or non-existent ISO code are left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single `iso` parameter is fully documented in-schema as a required two-character uppercase code. The description reinforces the input domain by framing the lookup as a country profile keyed by that code, adding modest but real meaning without contradicting the schema.

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

Purpose5/5

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

States a specific verb and resource ("Returns only the public country profile metadata (country name and code)") and names the source API. The closing clause explicitly distinguishes it from the club/player enumeration tools in the sibling set, so an agent can identify what this tool is without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The negative scoping ("does not enumerate players or clubs") clearly tells the agent when not to reach for this tool and implicitly routes it to the club/player tools. It lacks an explicit positive trigger such as "use when you already have an ISO code and need the country name," which keeps it short of a 5.

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?