clan_membersClash 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.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | Yes | ||
| after | No | ||
| limit | No | ||
| before | No |
| Name | Required | Description | Default |
|---|---|---|---|
| items | No | List of clan members | |
| paging | No | Pagination info |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "tag": "#2CCCP"
+ },
+ {
+ "limit": 50,
+ "tag": "#2CCCP"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "items": {
+ "description": "List of clan members",
+ "items": {
+ "properties": {
+ "arena": {
+ "description": "Current arena",
+ "type": "object"
+ },
+ "clanChestCrowns": {
+ "description": "Clan chest crowns",
+ "type": "number"
+ },
+ "clanRank": {
+ "description": "Rank in clan",
+ "type": "number"
+ },
+ "donations": {
+ "description": "Cards donated",
+ "type": "number"
+ },
+ "donationsReceived": {
+ "description": "Cards received",
+ "type": "number"
+ },
+ "expLevel": {
+ "description": "Experience level",
+ "type": "number"
+ },
+ "name": {
+ "description": "Member name",
+ "type": "string"
+ },
+ "previousClanRank": {
+ "description": "Previous clan rank",
+ "type": "number"
+ },
+ "role": {
+ "description": "Member role",
+ "type": "string"
+ },
+ "tag": {
+ "description": "Member 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"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds behavioral detail about pagination via limit/after/before cursors and the output fields, which is useful beyond the structured annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. Purpose, resource, output fields, and pagination are all front-loaded and fully specified.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With rich annotations and an output schema present, the description covers the essential context: official API, member fields, and pagination. Nothing critical is missing for a straightforward list operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It clarifies 'tag' as a clan tag and mentions limit/after/before as cursors, but does not explain their exact semantics (e.g., the meaning of 'after' vs 'before'). This is partial but insufficient for full compensation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb+resource: 'paginated member list for a clan tag' and enumerates specific fields (name, role, trophies, last active, donations). This distinguishes it from sibling tools like 'clan' or 'clan_war_log' by scoping to member data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context: use this to list members of a specific clan via its tag, with pagination. It does not explicitly mention alternatives or when-not-to-use, but the context is unambiguous given the tool name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.