Skip to main content
Glama

Clash Royale Locations

clash_royale_locations
Read-onlyIdempotent

Clash Royale official API, full list of supported location IDs (countries + global) used by ranking endpoints such as rankings_clans and rankings_players.

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": {},
    "name": "clash_royale_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds only that the data is an official full list of countries plus a global entry; it does not say whether the result is stable/static reference data or whether it may change, which is the one behavioral trait left unstated for a 0-parameter lookup.

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 front-loaded sentence with no filler; the resource, its scope, and its downstream use all appear before any trailing detail. Nothing is repeated from the schema or annotations.

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?

An output schema exists, so return values need no explanation, and the tool takes no arguments, making this a simple reference lookup that the one sentence adequately covers. Only a hint about the singular clash_royale_location alternative or data stability keeps it from being fully complete.

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?

There are zero input parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends no words on arguments.

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 resource and scope: the full, official list of supported location IDs, with the clarifying parenthetical "(countries + global)". It reads clearly as a list/reference endpoint, though it never explicitly contrasts itself with the singular sibling clash_royale_location, so the agent must infer singular-vs-list from the names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Names the consuming endpoints ('rankings_clans and rankings_players'), which tells an agent this is the lookup to call before issuing a rankings request with a location ID. It stops short of an explicit ordering instruction or a when-not-to-use note, but the usage context is clear rather than implied.

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.