Skip to main content
Glama

Clash Royale

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Rankings Players

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
locationIdYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoRanked players
pagingNoPagination info

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "locationId": 57000
+  },
+  {
+    "limit": 50,
+    "locationId": 57000
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "description": "Ranked players",
+      "items": {
+        "properties": {
+          "arena": {
+            "description": "Arena info",
+            "type": "object"
+          },
+          "clan": {
+            "description": "Clan info",
+            "type": "object"
+          },
+          "expLevel": {
+            "description": "Experience level",
+            "type": "number"
+          },
+          "name": {
+            "description": "Player name",
+            "type": "string"
+          },
+          "previousRank": {
+            "description": "Previous ranking",
+            "type": "number"
+          },
+          "rank": {
+            "description": "Ranking position",
+            "type": "number"
+          },
+          "tag": {
+            "description": "Player tag",
+            "type": "string"
+          },
+          "trophies": {
+            "description": "Trophy count",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "paging": {
+      "description": "Pagination info",
+      "properties": {
+        "cursors": {
+          "description": "Pagination cursors",
+          "type": "object"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already communicate read-only, idempotent, and non-destructive behavior. The description adds context by listing the returned data fields and noting it's the official API, which is useful but not exhaustive (e.g., no pagination behavior mentioned).

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?

Two concise sentences deliver the essential purpose and a usage hint without redundancy. The information is front-loaded and every word serves a purpose.

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 simple read-only tool with an output schema present, the description sufficiently covers scope, fields, and location semantics. It omits limit details but that is a minor gap given the tool's simplicity.

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?

The description explains locationId meaning and the global ID special value, but does not describe the 'limit' parameter at all. With 0% schema coverage, this partial compensation is adequate but leaves a gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns top-ranked players for a given location, listing specific fields (name, tag, trophies, etc.). The scope is explicit and the name distinguishes it from sibling rankings_clans.

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?

It provides a usage tip ('Use global ID for worldwide rankings') but does not explicitly differentiate when to use this tool vs alternatives like rankings_clans. The guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Clash Royale toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources