Skip to main content
Glama

Clash Royale Rankings Players

clash_royale_rankings_players
Read-onlyIdempotent

Clash Royale official API, top-ranked players for a location ID (numeric): player name, tag, trophies, exp level, clan, and rank position. Use global ID for worldwide rankings.

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": {
      "locationId": 57000
    },
    "name": "clash_royale_rankings_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
locationIdYes

Output Schema

NameRequiredDescriptionDefault
itemsNoRanked players
pagingNoPagination info

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that this hits the official Clash Royale API and what data comes back, but says nothing about result-set size caps, rate limits, or how the `limit` parameter changes behavior.

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 dense sentences with the resource and scope front-loaded, then the usage caveat. The field enumeration is mildly redundant given an output schema exists, but it is compact and not padded.

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?

For a simple two-parameter read tool with annotations and an output schema, most of the burden is already carried elsewhere. The remaining gap is the undocumented `limit` parameter and the absence of any note on maximum page size, which an agent needs to paginate correctly.

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 description coverage is 0%, so the description must carry parameter meaning. It does explain locationId as a numeric location with the 'global' ID for worldwide rankings, but the `limit` parameter is entirely undocumented in both the schema and the description, leaving half the parameters opaque.

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+resource: top-ranked players for a location ID, and enumerates the returned fields (name, tag, trophies, exp level, clan, rank). An agent can distinguish this from clash_royale_player (single player) and rankings_clans, though neither 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?

One concrete usage hint is given: use the global ID for worldwide rankings. However, there is no guidance on when to prefer this over clash_royale_player or rankings_clans, and no mention of the locationId values that are valid beyond 'numeric'.

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.