Skip to main content
Glama

Clash Royale

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Player Battles

player_battles
Read-onlyIdempotent

Clash Royale official API — recent battle log for a player tag: outcome, decks used, opponent, arena, and trophy change for each of the last ~25 battles.

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": {
+          "arena": {
+            "description": "Arena info",
+            "type": "object"
+          },
+          "battleTime": {
+            "description": "Battle timestamp",
+            "type": "string"
+          },
+          "crowns": {
+            "description": "Crowns earned by player",
+            "type": "number"
+          },
+          "deck": {
+            "description": "Player deck cards",
+            "type": "array"
+          },
+          "elixirLeaked": {
+            "description": "Elixir leaked",
+            "type": "number"
+          },
+          "gameMode": {
+            "description": "Game mode details",
+            "type": "object"
+          },
+          "opponent": {
+            "description": "Opponent info",
+            "type": "object"
+          },
+          "opponentCrowns": {
+            "description": "Opponent crowns",
+            "type": "number"
+          },
+          "opponentElixirLeaked": {
+            "description": "Opponent elixir leaked",
+            "type": "number"
+          },
+          "teamCrowns": {
+            "description": "Team crowns earned",
+            "type": "number"
+          },
+          "type": {
+            "description": "Battle type",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, open-world, idempotent, and non-destructive. The description adds valuable context beyond these, including that it is from the 'official Clash Royale API', returns the 'last ~25 battles', and specifies the included data fields. No contradictions with 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, well-structured sentence that front-loads the source ('Clash Royale official API') and the core function ('recent battle log'). It conveys the key details without any wasted words, making it highly concise and readable.

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?

Given the tool's simplicity (one parameter, read-only, with an output schema), the description covers the essential behavior and result content. It mentions the approximate count of battles and the data fields, though it does not address potential error cases or rate limits. Overall, it is sufficient for an agent to select and invoke the tool correctly.

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

Parameters2/5

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

Schema coverage is 0% (the schema only provides the parameter name and type), so the description carries the full burden. It says 'for a player tag' but does not explain the tag format, whether the '#' is required, URL-encoding needs, or any constraints. The example in the schema helps, but the description itself adds minimal semantic value beyond what the parameter name already implies.

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 returns 'recent battle log for a player tag' and lists specific data fields (outcome, decks, opponent, arena, trophy change), making the purpose unambiguous. It also distinguishes itself from sibling tools like 'player' and 'player_upcoming_chests' by focusing specifically on battles.

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?

The description implies usage when you need a player's recent battles, and the 'for a player tag' phrase suggests the input requirement. However, it provides no explicit guidance on when to use this tool over alternatives such as 'player' or 'rankings_players', nor any exclusions or prerequisites.

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