Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

chesscom: Get player stats

chesscom_get_player_stats
Read-onlyIdempotent

Retrieve a Chess.com player's ratings, best scores, and win/loss/draw records by time control (daily, rapid, blitz, bullet) and chess960 using their username.

Instructions

Get a Chess.com player's stats by time control (daily, rapid, blitz, bullet) and chess960, with current ratings, best, and W/L/D records.

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
usernameYesChess.com username (case-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Keys to keep (comma-separated).",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile needs no restating. The description adds useful context about the response grouping by time control and the record fields, but says nothing about rate limits, invalid/unknown usernames, or whether all time controls are returned in one call.

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 that opens with the verb and resource and spends its remainder on the returned breakdown. No filler, no repetition of the title.

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 carries the return-shape burden by naming ratings, best, and W/L/D per time control. It is nearly complete for a simple read-only stats fetch, lacking only edge-case behavior (unknown username, partial coverage of time controls).

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% with only two params (username, fields), so the schema already carries both. The description's 'by time control (daily, rapid, blitz, bullet) and chess960' actually describes the result grouping rather than any parameter, so it adds no parameter-level syntax or format guidance beyond the schema. 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?

States a specific verb and resource ('Get a Chess.com player's stats') and enumerates the covered time controls plus the data returned (current ratings, best, W/L/D). It clearly separates itself from chesscom_get_player in substance, though it never names a sibling for explicit routing.

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 only implied: an agent can infer this is the tool for a player's rating/record breakdown rather than their profile or club list. There is no when-to-use/when-not guidance, no note on what chesscom_get_player covers instead, and no prerequisites (e.g. username validity).

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