Skip to main content
Glama

Clash Royale

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Clan War Log

clan_war_log
Read-onlyIdempotent

Clash Royale official API — war log for a clan tag: past war seasons with participants, battles played, wins, and final standings. Supports limit/after/before cursors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagYes
afterNo
limitNo
beforeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoWar log entries
pagingNoPagination info

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "tag": "#2CCCP"
+  },
+  {
+    "limit": 10,
+    "tag": "#2CCCP"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "description": "War log entries",
+      "items": {
+        "properties": {
+          "clan": {
+            "description": "Clan info",
+            "type": "object"
+          },
+          "createdDate": {
+            "description": "War creation date",
+            "type": "string"
+          },
+          "opponent": {
+            "description": "Opponent clan info",
+            "type": "object"
+          },
+          "opponentCrowns": {
+            "description": "Opponent crowns",
+            "type": "number"
+          },
+          "participants": {
+            "description": "War participants",
+            "type": "array"
+          },
+          "seasonId": {
+            "description": "Season ID",
+            "type": "number"
+          },
+          "teamCrowns": {
+            "description": "Team crowns",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "paging": {
+      "description": "Pagination info",
+      "properties": {
+        "cursors": {
+          "description": "Pagination cursors",
+          "type": "object"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "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 declare readOnlyHint=true and destructiveHint=false, establishing the safe read-only nature. The description adds that it is the official Clash Royale API and lists the data content, but does not elaborate on pagination behavior beyond cursor support, so the annotations carry the burden.

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 sentence that front-loads the purpose and includes essential details about data and cursors. No filler or duplication.

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?

With an output schema present and annotations summarizing the safety profile, the description is largely complete for selection and invocation. The only minor gap is the lack of explicit alternatives, but given the clear distinction from sibling tools, this is sufficient.

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?

Schema description coverage is 0%, but the description clarifies that 'tag' is a clan tag and that 'limit/after/before' are cursor parameters. This adds some meaning beyond the raw schema, though it doesn't explain the exact semantics of the cursors.

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 retrieves the war log for a clan tag, including past war seasons with participants, battles, wins, and final standings. This specific verb+resource distinguishes it from sibling tools like clan_current_war and clan_members.

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 notes 'past war seasons,' clearly indicating this is for historical data, which implies it is the correct choice over clan_current_war for past conflicts. It does not explicitly name alternatives but provides clear contextual guidance.

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