Skip to main content
Glama

Clash Royale

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Player Upcoming Chests

player_upcoming_chests
Read-onlyIdempotent

Clash Royale official API — upcoming chest cycle for a player tag: chest type and position index for the next chests in queue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "tag": "#2P8888R"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "index": {
+            "description": "Position in chest queue",
+            "type": "number"
+          },
+          "name": {
+            "description": "Chest name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds that this is from the official Clash Royale API and specifies the returned data (chest type and position index). It does not contradict annotations, and any additional behavioral details like rate limits are absent but not critical given the annotations.

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?

The description is a single, concise sentence that front-loads the key context (official API) and immediately states the tool's purpose. Every word earns its place, with no redundant or filler content.

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 simple one-parameter read-only tool, this description is adequate. Rich annotations and an output schema cover safety, and the description clarifies the core purpose. It does not address every possible edge case, but none are critical for this level of complexity.

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 only parameter, 'tag', is described as a 'player tag' in the description, but no format specifics (e.g., # prefix) are provided. The schema example includes '#2P8888R', which partially compensates, but the description itself adds minimal meaning beyond the parameter name.

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?

The description clearly identifies the tool as retrieving the upcoming chest cycle for a player tag, with specific mention of chest type and position index. It distinguishes this from sibling tools by focusing exclusively on chest cycle data, though it lacks an explicit verb like 'get' or 'list'.

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: use when you need a player's upcoming chest cycle given their tag. However, there is no explicit guidance on when to use this tool versus alternatives, nor any mention of alternatives or exclusions.

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

All Clash Royale toolsInspect
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.

Resources