Skip to main content
Glama

Clash Royale Clan Members

clash_royale_clan_members
Read-onlyIdempotent

Clash Royale official API, paginated member list for a clan tag: each member's name, role, trophies, last active, and donations. Supports limit/after/before cursors.

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": {
      "tag": "#2CCCP"
    },
    "name": "clash_royale_clan_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes
afterNo
limitNo
beforeNo

Output Schema

NameRequiredDescriptionDefault
itemsNoList of clan members
pagingNoPagination info

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds meaningfully beyond them by disclosing pagination via cursors and the per-member fields returned. It omits rate-limit or API-key considerations, which keeps it from a 5.

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 front-loaded sentences with no filler; the pagination note earns its place. The field enumeration is slightly redundant given an output schema exists.

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 read-only paginated list tool with an output schema, the description covers purpose, returned fields, and pagination mechanics, which is sufficient. The remaining gap is precise cursor and tag-format semantics.

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?

With 0% schema description coverage, the description must compensate: it names limit/after/before as cursors and ties 'tag' to the clan, which is real added value. However, it never explains cursor semantics (e.g., whether after/before take member tags or timestamps) or the tag's required format, leaving half the parameters ambiguous.

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 and resource ('paginated member list for a clan tag') and enumerates returned fields, so an agent can distinguish it from clan-level tools like clash_royale_clan. It does not name a sibling explicitly, keeping it just below the top of the scale.

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 by the verb 'member list for a clan tag'; the description never says when to prefer this over clan_search or clash_royale_player, nor does it state prerequisites such as needing a valid clan tag or authentication.

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.