Skip to main content
Glama

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.

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_war_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes
afterNo
limitNo
beforeNo

Output 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

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is fully covered. The description adds only that cursors are supported, without saying how far back history goes, what the default page size is, or which direction the cursors travel.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact clauses, front-loaded with the API and resource, and the payload fields are enumerated efficiently. No filler, though the cursor sentence is a bare list rather than actionable detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the purpose is clear. However, pagination semantics and clan-tag encoding are left ambiguous for a four-parameter tool with zero schema documentation.

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% across four parameters, so the description must carry the burden. It names limit/after/before but explains none of them: no default limit, no indication whether 'after' moves toward newer or older seasons, and no tag format guidance beyond the example value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource and scope: 'war log for a clan tag: past war seasons with participants, battles played, wins, and final standings.' The word 'past' implicitly separates it from a current-war tool, but no sibling is named explicitly.

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?

Usage is implied by 'past war seasons' rather than stated — an agent can infer this is the historical counterpart to a current-war call, but there is no explicit when-to-use/when-not-to-use or named alternative.

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.