Skip to main content
Glama

Rankings Clans

rankings_clans
Read-onlyIdempotent

Clash Royale official API, top-ranked clans for a location ID (numeric): clan name, tag, score, member count, 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": "rankings_clans"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
locationIdYes

Output Schema

NameRequiredDescriptionDefault
itemsNoRanked clans
pagingNoPagination info

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "locationId": 57000
      +  },
      +  {
      +    "limit": 25,
      +    "locationId": 57000
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "items": {
      +      "description": "Ranked clans",
      +      "items": {
      +        "properties": {
      +          "badgeId": {
      +            "description": "Badge ID",
      +            "type": "number"
      +          },
      +          "clanScore": {
      +            "description": "Clan score",
      +            "type": "number"
      +          },
      +          "location": {
      +            "description": "Location",
      +            "type": "object"
      +          },
      +          "memberCount": {
      +            "description": "Member count",
      +            "type": "number"
      +          },
      +          "name": {
      +            "description": "Clan name",
      +            "type": "string"
      +          },
      +          "previousRank": {
      +            "description": "Previous ranking",
      +            "type": "number"
      +          },
      +          "rank": {
      +            "description": "Ranking position",
      +            "type": "number"
      +          },
      +          "tag": {
      +            "description": "Clan tag",
      +            "type": "string"
      +          },
      +          "type": {
      +            "description": "Clan type",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "paging": {
      +      "description": "Pagination info",
      +      "properties": {
      +        "cursors": {
      +          "description": "Pagination cursors",
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare the operation read-only, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds that this is the official API and enumerates the returned fields, which is useful context, but says nothing about pagination, rate limits, or result ordering beyond rank position.

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?

The definition is compact and front-loaded: one sentence defines the resource and returned fields, followed by a short directive on the worldwide ID. The listed return fields are slightly redundant given the output schema but do not bloat the text.

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?

With an output schema present, return values needn't be explained, and annotations cover safety and idempotency. However, the lack of limit semantics and the absence of any pointer on obtaining a valid locationId leave meaningful gaps for a two-parameter ranked-list tool.

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

Parameters2/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, and it only partially does: it explains that locationId is numeric and that the global ID yields worldwide rankings. The limit parameter is never mentioned — no default, maximum, or range — leaving half the parameters undocumented.

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 states a specific verb and resource ('top-ranked clans for a location ID') and lists the returned fields, so the agent knows exactly what data comes back. It does not differentiate from siblings such as clan_search or clash_royale_rankings_players, leaving the agent to infer the distinction from the name alone.

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?

The only usage guidance is 'Use global ID for worldwide rankings', which is a parameter tip rather than tool-selection guidance. There is no statement of when to choose this over clan_search or rankings_players, and no mention that the locationId must come from the locations endpoint.

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.