Skip to main content
Glama

chess

by io.github.pipeworx-io

Get Stats

get_stats
Read-onlyIdempotent

Get a CHESS.COM player's ratings and game records across daily, rapid, blitz, and bullet formats. PREFER for "'s blitz/bullet/rapid rating on Chess.com", "what is rated on Chess.com". Returns current/best ratings and win/loss/draw counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesChess.com username

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fideYesFIDE rating if available
blitzYes
dailyYes
rapidYes
bulletYes
usernameYesChess.com username
daily_960Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "username": "hikaru"
+  },
+  {
+    "username": "magnuscarlsen"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "blitz": {
+      "properties": {
+        "best_rating": {
+          "description": "Best rating achieved in blitz format",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "current_rating": {
+          "description": "Current rating in blitz format",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "record": {
+          "properties": {
+            "draw": {
+              "description": "Number of draws",
+              "type": "number"
+            },
+            "loss": {
+              "description": "Number of losses",
+              "type": "number"
+            },
+            "win": {
+              "description": "Number of wins",
+              "type": "number"
+            }
+          },
+          "type": [
+            "object",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "bullet": {
+      "properties": {
+        "best_rating": {
+          "description": "Best rating achieved in bullet format",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "current_rating": {
+          "description": "Current rating in bullet format",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "record": {
+          "properties": {
+            "draw": {
+              "description": "Number of draws",
+              "type": "number"
+            },
+            "loss": {
+              "description": "Number of losses",
+              "type": "number"
+            },
+            "win": {
+              "description": "Number of wins",
+              "type": "number"
+            }
+          },
+          "type": [
+            "object",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "daily": {
+      "properties": {
+        "best_rating": {
+          "description": "Best rating achieved in daily format",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "current_rating": {
+          "description": "Current rating in daily format",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "record": {
+          "properties": {
+            "draw": {
+              "description": "Number of draws",
+              "type": "number"
+            },
+            "loss": {
+              "description": "Number of losses",
+              "type": "number"
+            },
+            "win": {
+              "description": "Number of wins",
+              "type": "number"
+            }
+          },
+          "type": [
+            "object",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "daily_960": {
+      "properties": {
+        "best_rating": {
+          "description": "Best rating achieved in daily 960 format",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "current_rating": {
+          "description": "Current rating in daily 960 format",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "record": {
+          "properties": {
+            "draw": {
+              "description": "Number of draws",
+              "type": "number"
+            },
+            "loss": {
+              "description": "Number of losses",
+              "type": "number"
+            },
+            "win": {
+              "description": "Number of wins",
+              "type": "number"
+            }
+          },
+          "type": [
+            "object",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "fide": {
+      "description": "FIDE rating if available",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "rapid": {
+      "properties": {
+        "best_rating": {
+          "description": "Best rating achieved in rapid format",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "current_rating": {
+          "description": "Current rating in rapid format",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "record": {
+          "properties": {
+            "draw": {
+              "description": "Number of draws",
+              "type": "number"
+            },
+            "loss": {
+              "description": "Number of losses",
+              "type": "number"
+            },
+            "win": {
+              "description": "Number of wins",
+              "type": "number"
+            }
+          },
+          "type": [
+            "object",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "username": {
+      "description": "Chess.com username",
+      "type": "string"
+    }
+  },
+  "required": [
+    "username",
+    "fide",
+    "daily",
+    "rapid",
+    "blitz",
+    "bullet",
+    "daily_960"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "_apiKey": "your-sendgrid-api-key",
-    "start_date": "2024-01-01"
-  },
-  {
-    "_apiKey": "your-sendgrid-api-key",
-    "end_date": "2024-01-31",
-    "start_date": "2024-01-01"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "description": "Email sending statistics for a date range",
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Email sending statistics for a date range",
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-sendgrid-api-key",
+    "start_date": "2024-01-01"
+  },
+  {
+    "_apiKey": "your-sendgrid-api-key",
+    "end_date": "2024-01-31",
+    "start_date": "2024-01-01"
+  }
+]
  5. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile. The description adds that it returns current/best ratings and win/loss/draw counts, but doesn't discuss rate limits, data freshness, or error behavior. With annotations covering safety, the added context is useful but not rich.

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 sentences, front-loaded with the main purpose, and includes practical usage trigger examples. No redundant filler; every sentence earns its place.

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?

For a one-parameter read-only tool with full annotations and an output schema, the description provides the function, scope, and example usage. It doesn't mention edge cases or limitations, but those aren't critical given the tool's simplicity and rich structured metadata.

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?

The single 'username' parameter has full schema coverage ('Chess.com username'). The description doesn't add further meaning about parameter format or constraints, so baseline 3 is appropriate.

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?

Description states 'Get a CHESS.COM player's ratings and game records across daily, rapid, blitz, and bullet formats' – a specific verb, resource, and scope. It also includes concrete example queries, making the tool's purpose unmistakable and distinguishing it from generic get_games/get_player tools.

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?

Explicitly says 'PREFER for' with natural language examples, guiding the agent on when to select this tool. It doesn't mention what it should NOT be used for or name alternatives, which keeps it from a 5, but the guidance is clear and actionable.

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

All chess toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

The server is named 'chess', yet none of the 34 tools relate to chess. An agent looking for chess functionality would find all tools irrelevant. While individual tool descriptions are clear, the server's name creates a fundamental disambiguation problem: the tool set does not match the server's apparent purpose.

Naming Consistency4/5

Tool names within the set follow a consistent snake_case pattern with descriptive verbs (e.g., ask_pipeworx, deep_research, resolve_entity). There are no mixed conventions. However, the server name 'chess' is completely inconsistent with the tool names, which all suggest data research rather than chess.

Tool Count1/5

For a server named 'chess', 34 tools is wildly excessive. Even for a data research server, the count is high, but the server's name implies a narrow chess domain, making the count inappropriate. The tools cover broad topics like SEC filings, Polymarket, and weather, none of which belong in a chess server.

Completeness1/5

The server claims to be about chess, but there are zero chess-related tools. The tool set is completely incomplete for its stated purpose. As a data research server, completeness might be high, but that is irrelevant given the server name.

Resources