Skip to main content
Glama

Clash Royale

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Cards

cards
Read-onlyIdempotent

Clash Royale official API — complete list of all game cards: name, max level, elixir cost, rarity, type, arena, and icon URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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: +[
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "arena": {
+            "description": "Arena unlock level",
+            "type": "number"
+          },
+          "description": {
+            "description": "Card description",
+            "type": "string"
+          },
+          "elixirCost": {
+            "description": "Elixir cost",
+            "type": "number"
+          },
+          "iconUrls": {
+            "description": "Icon URLs",
+            "type": "object"
+          },
+          "id": {
+            "description": "Card ID",
+            "type": "number"
+          },
+          "key": {
+            "description": "Card key identifier",
+            "type": "string"
+          },
+          "maxLevel": {
+            "description": "Maximum card level",
+            "type": "number"
+          },
+          "name": {
+            "description": "Card name",
+            "type": "string"
+          },
+          "rarity": {
+            "description": "Card rarity",
+            "type": "string"
+          },
+          "type": {
+            "description": "Card type",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety and behavioral profile is well covered. The description adds that it comes from the official API and lists the returned fields, but does not disclose further behaviors like pagination or rate limits. Given the strong annotation coverage, this is adequate.

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 main purpose ('complete list of all game cards') and then lists the included fields. Every word earns its place with zero unnecessary filler.

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, parameterless list tool with a rich set of annotations and an output schema, the description is largely complete. It clearly states the resource and return fields. Additional context like pagination or sorting is not needed for a 'complete list' endpoint, though a bit more detail on how the list is ordered could enhance completeness.

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

Parameters4/5

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

The tool has zero parameters, so schema coverage is trivially 100%. Baseline for 0-parameter tools is 4, and the description doesn't need to explain parameters. It adds no parameter-specific info, but none is required.

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 identifies the tool's purpose: retrieving the complete list of all Clash Royale cards, with a specific verb ('complete list') and resource ('cards'). It also enumerates the fields returned (name, max level, elixir cost, rarity, type, arena, icon URL), effectively distinguishing it from sibling tools like clan or player.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor any mention of exclusions. However, the description implies usage for obtaining the full card list, and for a simple parameterless resource the context is reasonably clear, but it lacks the explicit 'when to use' detail.

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