Clash Royale

Clan Current War

clan_current_war

Read-onlyIdempotent

Clash Royale official API — current war status for a clan tag: war state, collection-day and war-day results, participants, battles remaining, and standings.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tag`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`clan`	No	Clan info
`state`	No	War state
`opponent`	No	Opponent clan info
`battleTime`	No	Battle time
`participants`	No	Clan participants
`warStartTime`	No	War start timestamp

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "tag": "#2CCCP"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "battleTime": {
+      "description": "Battle time",
+      "type": "string"
+    },
+    "clan": {
+      "description": "Clan info",
+      "type": "object"
+    },
+    "opponent": {
+      "description": "Opponent clan info",
+      "type": "object"
+    },
+    "participants": {
+      "description": "Clan participants",
+      "type": "array"
+    },
+    "state": {
+      "description": "War state",
+      "type": "string"
+    },
+    "warStartTime": {
+      "description": "War start timestamp",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds the specific output contents, but this is largely redundant with the output schema. It does not add context on rate limits, auth, or other behavioral traits beyond what annotations provide.

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 purpose. Every clause adds relevant detail without wasted words.

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 a simple one-parameter tool, an output schema, and comprehensive annotations, the description sufficiently covers the tool's purpose and scope. It does not mention error cases or prerequisites, but these are not critical given the low complexity and presence of structured metadata.

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 description coverage is 0%, so the description must compensate for parameter meaning. It only says 'for a clan tag', which merely restates the parameter name without explaining format (e.g., required '#' prefix, encoding) or constraints. The example in the schema is not part of the description, so semantics are inadequate.

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 states a specific verb+resource: 'current war status for a clan tag' and enumerates the exact data returned (war state, collection-day and war-day results, participants, battles remaining, standings). This clearly distinguishes it from sibling tools like clan_war_log (historical wars) and clan (general info).

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 for current war status but does not explicitly contrast it with alternatives like clan_war_log or mention when not to use it. There is no explicit when/when-not guidance, only an implied scope based on the name and description.

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

All Clash Royale tools Inspect

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.