chess

Get Leaderboards

get_leaderboards

Read-onlyIdempotent

Check top-ranked Chess.com players by format (daily, rapid, blitz, bullet). Returns rankings with ratings and win percentages.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`daily`	Yes	Top 10 daily format players
`tactics`	Yes	Top 10 tactics puzzle players
`live_blitz`	Yes	Top 10 blitz format players
`live_rapid`	Yes	Top 10 rapid format players
`live_bullet`	Yes	Top 10 bullet format players

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "daily": {
+      "description": "Top 10 daily format players",
+      "items": {
+        "properties": {
+          "rank": {
+            "description": "Player rank on leaderboard",
+            "type": "number"
+          },
+          "score": {
+            "description": "Player score/rating",
+            "type": "number"
+          },
+          "username": {
+            "description": "Chess.com username",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "live_blitz": {
+      "description": "Top 10 blitz format players",
+      "items": {
+        "properties": {
+          "rank": {
+            "description": "Player rank on leaderboard",
+            "type": "number"
+          },
+          "score": {
+            "description": "Player score/rating",
+            "type": "number"
+          },
+          "username": {
+            "description": "Chess.com username",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "live_bullet": {
+      "description": "Top 10 bullet format players",
+      "items": {
+        "properties": {
+          "rank": {
+            "description": "Player rank on leaderboard",
+            "type": "number"
+          },
+          "score": {
+            "description": "Player score/rating",
+            "type": "number"
+          },
+          "username": {
+            "description": "Chess.com username",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "live_rapid": {
+      "description": "Top 10 rapid format players",
+      "items": {
+        "properties": {
+          "rank": {
+            "description": "Player rank on leaderboard",
+            "type": "number"
+          },
+          "score": {
+            "description": "Player score/rating",
+            "type": "number"
+          },
+          "username": {
+            "description": "Chess.com username",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tactics": {
+      "description": "Top 10 tactics puzzle players",
+      "items": {
+        "properties": {
+          "rank": {
+            "description": "Player rank on leaderboard",
+            "type": "number"
+          },
+          "score": {
+            "description": "Player score/rating",
+            "type": "number"
+          },
+          "username": {
+            "description": "Chess.com username",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "daily",
+    "live_rapid",
+    "live_blitz",
+    "live_bullet",
+    "tactics"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {}
+]
```
First observedApr 14, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds that the tool returns rankings with ratings and win percentages, but since an output schema exists, this adds limited extra value. No contradictions found.

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?

Efficient single sentence that covers purpose and return content without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with an output schema and solid annotations, the description is complete. It covers what data is returned and the organization by format.

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

Parameters5/5

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

The tool has no parameters, so the baseline is 4. The description adds meaning by listing the valid formats (daily, rapid, blitz, bullet), which is not present in the empty schema, making it highly informative.

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?

The description clearly states the tool's function: checking top-ranked Chess.com players, and lists specific formats (daily, rapid, blitz, bullet). This distinguishes it from related tools like get_games or get_player.

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 description implies usage for leaderboard queries, but does not explicitly mention when not to use it or name alternatives. However, the context is clear from the tool name and sibling tools.

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

All chess 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.