Skip to main content
Glama

Clash Royale Player

clash_royale_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.

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

Input Schema

NameRequiredDescriptionDefault
tagYes

Output Schema

NameRequiredDescriptionDefault
tagNoPlayer tag identifier
clanNoClan membership info
nameNoPlayer name
winsNoTotal wins
arenaNoCurrent arena info
cardsNoPlayer cards
lossesNoTotal losses
expLevelNoExperience level
trophiesNoCurrent trophy count
battleCountNoTotal battles
currentDeckNoCurrent deck cards
bestTrophiesNoBest trophy count
threeCrownWinsNoThree crown wins
challengeMaxWinsNoChallenge max wins
leagueStatisticsNoLeague statistics
challengeCardsWonNoChallenge cards won
tournamentCardsWonNoTournament cards won
currentFavoriteDeckNoCurrent favorite deck

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds that this hits the 'official API' and gives the aggregate scope of the payload but says nothing about rate limits, tag-case handling, error behavior on invalid tags, or freshness of stats.

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?

A single well-formed sentence that front-loads the API and the resource, then lists payload contents. No filler, though the field list runs slightly long given an output schema already exists.

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 one-parameter read-only lookup with an output schema present, the description covers source, scope, and tag format adequately. Minor gaps remain around invalid-tag behavior and tag normalization, but nothing essential for a correct call is missing.

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?

Schema coverage is 0% for the single 'tag' parameter, so the description must carry the burden. It partially compensates by showing the expected format with a leading '#' ('#2PP...'), which is genuine meaning beyond the bare {type: string} schema, but it does not clarify case sensitivity, URL-encoding, or whether the '#' is required.

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?

States a specific verb-and-resource pair ('full profile for a player tag') and enumerates the contents returned (trophies, level, arena, clan, cards, battle stats, league ranking). This makes the distinction from clash_royale_player_battles reasonably inferable from 'full profile', though 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 Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no pointer to alternatives such as clash_royale_player_battles for battle-specific data. The only usage signal is the example tag format, which is invocation detail rather than tool selection guidance.

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.