Skip to main content
Glama

Clash Royale Location

clash_royale_location
Read-onlyIdempotent

Clash Royale official API, details for a single location by numeric ID: name, country code, and whether it is a country or a global region.

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": {
      "id": 57000
    },
    "name": "clash_royale_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
idNoLocation ID
nameNoLocation name
isCountryNoIs a country

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 API' and names the fields returned, but that field list is largely duplicated by the existing output schema, and it says nothing about caching or error behavior for unknown IDs.

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 front-loaded sentence with a colon-delimited field list and zero filler. It is dense but readable, and the scoping information ('single location by numeric ID') arrives before the field enumeration.

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?

This is a simple one-parameter read tool with full annotation coverage and an output schema, so the description does not need to explain return values. What remains is a reasonable statement of input domain and resource scope; only explicit sibling routing is absent.

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?

Schema coverage is 0% and the schema only supplies a bare number with an example of 57000. The description compensates by specifying that the id is a numeric location ID, which tells the agent the parameter's domain rather than leaving it ambiguous against player or clan tags.

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 uses a specific verb-and-resource construction ('details for a single location by numeric ID') and enumerates the returned fields (name, country code, country-vs-region flag). 'Single' implicitly contrasts with the plural sibling clash_royale_locations, though that sibling is never named.

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: the agent can infer this is the lookup to use when it already has a location ID. There is no explicit statement of when to prefer it over clash_royale_locations or clash_royale_rankings_players, and no prerequisites 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.