Clash Royale

Player

player

Read-onlyIdempotent

Clash Royale official API — full profile for a player tag (#2PP…): trophies, level, arena, clan, card collection, battle stats, and league ranking.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tag`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Player tag identifier
`clan`	No	Clan membership info
`name`	No	Player name
`wins`	No	Total wins
`arena`	No	Current arena info
`cards`	No	Player cards
`losses`	No	Total losses
`expLevel`	No	Experience level
`trophies`	No	Current trophy count
`battleCount`	No	Total battles
`currentDeck`	No	Current deck cards
`bestTrophies`	No	Best trophy count
`threeCrownWins`	No	Three crown wins
`challengeMaxWins`	No	Challenge max wins
`leagueStatistics`	No	League statistics
`challengeCardsWon`	No	Challenge cards won
`tournamentCardsWon`	No	Tournament cards won
`currentFavoriteDeck`	No	Current favorite deck

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "tag": "#2P8888R"
+  },
+  {
+    "tag": "#Y92V0L9"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "arena": {
+      "description": "Current arena info",
+      "type": "object"
+    },
+    "battleCount": {
+      "description": "Total battles",
+      "type": "number"
+    },
+    "bestTrophies": {
+      "description": "Best trophy count",
+      "type": "number"
+    },
+    "cards": {
+      "description": "Player cards",
+      "type": "array"
+    },
+    "challengeCardsWon": {
+      "description": "Challenge cards won",
+      "type": "number"
+    },
+    "challengeMaxWins": {
+      "description": "Challenge max wins",
+      "type": "number"
+    },
+    "clan": {
+      "description": "Clan membership info",
+      "type": "object"
+    },
+    "currentDeck": {
+      "description": "Current deck cards",
+      "type": "array"
+    },
+    "currentFavoriteDeck": {
+      "description": "Current favorite deck",
+      "type": "array"
+    },
+    "expLevel": {
+      "description": "Experience level",
+      "type": "number"
+    },
+    "leagueStatistics": {
+      "description": "League statistics",
+      "type": "object"
+    },
+    "losses": {
+      "description": "Total losses",
+      "type": "number"
+    },
+    "name": {
+      "description": "Player name",
+      "type": "string"
+    },
+    "tag": {
+      "description": "Player tag identifier",
+      "type": "string"
+    },
+    "threeCrownWins": {
+      "description": "Three crown wins",
+      "type": "number"
+    },
+    "tournamentCardsWon": {
+      "description": "Tournament cards won",
+      "type": "number"
+    },
+    "trophies": {
+      "description": "Current trophy count",
+      "type": "number"
+    },
+    "wins": {
+      "description": "Total wins",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, non-destructive. The description adds value by specifying the data returned and noting it's an official API, which implies potential rate limits or auth. No contradiction with annotations.

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?

A single, well-structured sentence that leads with the tool's purpose ('full profile') and then lists key returned data. No fluff or repetition of schema/annotations.

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

Completeness5/5

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

With an output schema available and only one parameter, the description sufficiently covers invocation and return value scope. It's complete for a simple read-only profile tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero description coverage for the 'tag' parameter, but the description explains the tag format using '#2PP…', giving the agent necessary context. This compensates for the schema gap.

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 fetches a full player profile for a Clash Royale player tag, listing specific data (trophies, level, arena, clan, cards, battle stats, ranking). This differentiates it from siblings like player_battles and player_upcoming_chests.

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 'full profile' but there is no explicit guidance on when to use this versus alternatives. It doesn't state exclusions or name other tools, so coverage of when-to-use is only implicit.

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.