Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tag": "#2CCCP"
    },
    "name": "clan_current_war"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes

Output Schema

NameRequiredDescriptionDefault
clanNoClan info
stateNoWar state
opponentNoOpponent clan info
battleTimeNoBattle time
participantsNoClan participants
warStartTimeNoWar start timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true), so the description only needs to add context. It adds a useful inventory of response content (war state, collection-day and war-day results, participants, battles remaining, standings), but it does not address the edge cases an agent would most need: a clan that is not currently at war, whether the call is expensive or rate-limited, or what the response looks like when the war is in the preparation phase.

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 definition is a single front-loaded sentence that leads with the API source and the resource and then itemizes the payload fields. Every clause carries information, and there is no filler or repetition.

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?

Because an output schema exists, the description does not need to explain return values, yet it still outlines the main response sections, which is helpful. Its only shortfall is the lack of guidance about war-state edge cases and tag formatting, which would matter for a tool that is only meaningful while a war is active.

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?

There is one parameter, and the schema gives it 0% description coverage; the only hint about its format comes from the schema's example '#2CCCP'. The description adds the meaning that this is a clan tag, which is slightly better than the bare 'tag' name, but it does not state the required '#' prefix or any format constraints, so the agent must infer the format from the example.

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 definition names a specific verb and resource ('Clash Royale official API, current war status for a clan tag') and enumerates the returned content, so an agent can immediately distinguish it from a war-history tool such as clan_war_log. The mention of 'current war status' also separates it from general clan lookups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to use this tool (for example, only when a clan is actively in a war) or when to prefer clan_war_log. It also omits prerequisites such as whether the tag must include the leading '#' or what happens when no war is active, leaving usage entirely inferred from the name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.