Skip to main content
Glama

Clash Royale Player Battles

clash_royale_player_battles
Read-onlyIdempotent

Clash Royale official API, recent battle log for a player tag: outcome, decks used, opponent, arena, and trophy change for each of the last ~25 battles.

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": "#2P8888R"
    },
    "name": "clash_royale_player_battles"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered structurally. The description adds genuinely useful behavior beyond that: the result is bounded to roughly the last ~25 battles and is not a full history. It does not mention authentication, rate limits, or what happens with an invalid/unknown tag.

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?

One front-loaded sentence that identifies the API source, the resource, and the returned fields with zero filler. The enumerated field list is slightly redundant given an output schema exists, which keeps it from being maximally tight.

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, single-parameter read tool with a full annotation set and an output schema, the definition covers scope and the ~25-battle cap, which is the one fact an agent could otherwise get wrong. Gaps are minor: tag formatting and error behavior.

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 a single required parameter with 0% schema description coverage, so the description carries the burden; it only says 'player tag' without explaining encoding (the leading '#') or normalization. The schema example '#2P8888R' partially compensates, but the description itself adds little beyond naming the concept.

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?

The description names a specific verb+resource ('recent battle log for a player tag') and enumerates the payload ('outcome, decks used, opponent, arena, and trophy change'), which lets an agent distinguish it from the profile-oriented clash_royale_player sibling. It stops short of naming an alternative explicitly, so it lands just below the top mark.

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 only implied: an agent can infer it should be called when historical battle results for one player are needed, but there is no explicit statement of when to prefer it over clash_royale_player or other siblings, and no prerequisites (valid tag format, API key, rate limits) are mentioned.

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.