Skip to main content
Glama

FoxAPIs data sources

chess.com player

chess_player
Read-onlyIdempotent

A chess.com player: ratings per time control, title, country, followers, puzzle and tactics ratings and last online date, by user name. Costs 1 credit a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": "chess_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesFor example: "hikaru"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety bar is largely met. The description adds genuinely useful context beyond them: a 1-credit cost per call, no charge for empty answers, and an API-key requirement — all operational facts an agent cannot get from structured fields.

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?

Two short segments: the first front-loads the resource and its returned fields, the second handles cost and auth. Nearly every clause earns its place; the '(free to start)' parenthetical is the only marketing filler.

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 no output schema, the description correctly compensates by enumerating the returned fields, and it covers the billing/auth model. Minor gaps remain — behavior for a nonexistent or unrated player and the set of valid time controls — but nothing that would prevent a correct call.

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 carries its own example ("hikaru"), so the schema does the work. The description only restates the key as 'user name' without adding format rules (case sensitivity, whether a full chess.com profile URL is accepted), so it sits at the baseline.

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?

Names a specific resource (a chess.com player) and enumerates exactly what comes back — per-time-control ratings, title, country, followers, puzzle/tactics ratings, last online date — keyed by user name. It is clearly distinguishable from lichess_player by the explicit chess.com scoping, though it never says so directly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer 'call this when you have a chess.com username and want that player's profile.' There is no explicit when-not guidance and no mention of lichess_player as the alternative for non-chess.com players, which is the one routing decision an agent actually faces here.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources