Skip to main content
Glama

chess

by io.github.pipeworx-io

Get Games

get_games
Read-onlyIdempotent

Retrieve a player's completed games for a specific month (format: YYYY/MM, e.g., '2024/01'). Returns game URLs, time controls, results, and ratings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesYear (e.g., 2024)
monthYesMonth as a number (1-12)
usernameYesChess.com username

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesYear of games
gamesYes
monthYesMonth of games (1-12)
usernameYesChess.com username
total_gamesYesTotal number of games in month

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: +[
+  {
+    "month": 1,
+    "username": "hikaru",
+    "year": 2024
+  },
+  {
+    "month": 12,
+    "username": "magnuscarlsen",
+    "year": 2024
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "games": {
+      "items": {
+        "properties": {
+          "black": {
+            "properties": {
+              "rating": {
+                "description": "Black player rating",
+                "type": "number"
+              },
+              "result": {
+                "description": "Black player result (win/loss/draw)",
+                "type": "string"
+              },
+              "username": {
+                "description": "Black player username",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "end_time": {
+            "description": "Game end time in ISO 8601 format",
+            "type": "string"
+          },
+          "rated": {
+            "description": "Whether game counted toward rating",
+            "type": "boolean"
+          },
+          "time_class": {
+            "description": "Game time class (e.g., rapid, blitz)",
+            "type": "string"
+          },
+          "time_control": {
+            "description": "Time control string (e.g., 15+2)",
+            "type": "string"
+          },
+          "url": {
+            "description": "URL to game on Chess.com",
+            "type": "string"
+          },
+          "uuid": {
+            "description": "Unique game identifier",
+            "type": "string"
+          },
+          "white": {
+            "properties": {
+              "rating": {
+                "description": "White player rating",
+                "type": "number"
+              },
+              "result": {
+                "description": "White player result (win/loss/draw)",
+                "type": "string"
+              },
+              "username": {
+                "description": "White player username",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "month": {
+      "description": "Month of games (1-12)",
+      "type": "number"
+    },
+    "total_games": {
+      "description": "Total number of games in month",
+      "type": "number"
+    },
+    "username": {
+      "description": "Chess.com username",
+      "type": "string"
+    },
+    "year": {
+      "description": "Year of games",
+      "type": "number"
+    }
+  },
+  "required": [
+    "username",
+    "year",
+    "month",
+    "total_games",
+    "games"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "season": 2024
-  },
-  {
-    "limit": 50,
-    "season": 2023
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "games": {
-      "description": "List of games",
-      "items": {
-        "properties": {
-          "date": {
-            "description": "Game date",
-            "type": "string"
-          },
-          "home_score": {
-            "description": "Home team score",
-            "type": "number"
-          },
-          "home_team": {
-            "description": "Home team full name",
-            "type": "string"
-          },
-          "id": {
-            "description": "Game ID",
-            "type": "number"
-          },
-          "period": {
-            "description": "Current period/quarter",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "postseason": {
-            "description": "Whether game is in postseason",
-            "type": "boolean"
-          },
-          "season": {
-            "description": "Season year",
-            "type": "number"
-          },
-          "status": {
-            "description": "Game status (Final, In Progress, etc.)",
-            "type": "string"
-          },
-          "time": {
-            "description": "Game time",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "visitor_score": {
-            "description": "Visiting team score",
-            "type": "number"
-          },
-          "visitor_team": {
-            "description": "Visiting team full name",
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "returned": {
-      "description": "Number of games returned in this response",
-      "type": "number"
-    },
-    "season": {
-      "description": "Season start year",
-      "type": "number"
-    },
-    "total": {
-      "description": "Total games in season",
-      "type": "number"
-    }
-  },
-  "required": [
-    "season",
-    "total",
-    "returned",
-    "games"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "games": {
+      "description": "List of games",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Game date",
+            "type": "string"
+          },
+          "home_score": {
+            "description": "Home team score",
+            "type": "number"
+          },
+          "home_team": {
+            "description": "Home team full name",
+            "type": "string"
+          },
+          "id": {
+            "description": "Game ID",
+            "type": "number"
+          },
+          "period": {
+            "description": "Current period/quarter",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "postseason": {
+            "description": "Whether game is in postseason",
+            "type": "boolean"
+          },
+          "season": {
+            "description": "Season year",
+            "type": "number"
+          },
+          "status": {
+            "description": "Game status (Final, In Progress, etc.)",
+            "type": "string"
+          },
+          "time": {
+            "description": "Game time",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "visitor_score": {
+            "description": "Visiting team score",
+            "type": "number"
+          },
+          "visitor_team": {
+            "description": "Visiting team full name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of games returned in this response",
+      "type": "number"
+    },
+    "season": {
+      "description": "Season start year",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total games in season",
+      "type": "number"
+    }
+  },
+  "required": [
+    "season",
+    "total",
+    "returned",
+    "games"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "season": 2024
+  },
+  {
+    "limit": 50,
+    "season": 2023
+  }
+]
  5. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already indicate a safe read-only, non-destructive, idempotent operation. The description adds context about the return payload (game URLs, time controls, results, ratings) and the date scoping, but does not disclose additional behavioral traits such as pagination, rate limits, or error handling. With annotations covering the safety profile, this is adequate 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 core action and resource, then returns info. Every word earns its place with no fluff or redundant details.

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 simple read-only tool with full parameter descriptions, an output schema, and comprehensive annotations, the description is complete. It states what the tool does, the date format, and the return content, leaving no major gaps.

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 input schema provides full coverage (100%) with descriptions for all three parameters (year, month, username). The description adds the combined 'YYYY/MM' format and an example, but this is somewhat redundant with the schema and even slightly inconsistent (separate year/month vs. combined format). It does not materially improve understanding beyond the schema, 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?

The description uses a specific verb ('Retrieve') and clearly identifies the resource (a player's completed games for a specific month), along with what it returns (game URLs, time controls, results, ratings). This distinguishes it from sibling tools like get_player and get_stats.

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 clearly specifies the use case: retrieving a player's completed games for a specific month, with a required date format. It does not explicitly name alternatives or exclusions, but the context is unambiguous for when this tool is appropriate.

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