Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

chesscom: Get country players

chesscom_get_country_players
Read-onlyIdempotent

Retrieve titled Chess.com players for a specified country, returning their usernames and titles.

Instructions

Get the list of titled Chess.com players from a country (returns usernames and titles).

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": {
      "country": "<country>"
    },
    "name": "chesscom_get_country_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
countryYesISO 3166 alpha-2 country code, e.g. "US", "FR", "IN"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety and volatility profile is fully covered without description help. The description adds return-content context ('returns usernames and titles'), which is useful given there is no output schema, but it omits volume, pagination, and any rate-limit caveats typical of external open-world APIs.

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?

A single front-loaded sentence states the action, the scope qualifier ('titled'), and the return payload. No filler or redundancy; every clause carries information.

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?

For a simple read-only, two-parameter lookup with full schema coverage and covering annotations, the description is close to sufficient and the return-content hint compensates for the absent output schema. However, it says nothing about result size, ordering, or pagination behavior for what may be a long country roster, leaving a modest 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%: 'country' is documented as an ISO 3166 alpha-2 code with examples and 'fields' as a comma-separated key list. The description adds nothing to the parameter semantics beyond what the schema already provides, 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+resource: retrieve the list of titled players from a country, with the 'titled' qualifier narrowing scope beyond a plain player listing. This is distinguishable from siblings like chesscom_get_player (single player) and chesscom_get_leaderboards (global ranking lists), though it does not explicitly name those siblings.

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 exclusions, and no routing to alternatives such as chesscom_get_leaderboards or chesscom_get_player. The agent must infer from the name that this is the country-scoped roster call, which is reasonable but not stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools