Skip to main content
Glama

Clash Royale Clan

clash_royale_clan
Read-onlyIdempotent

Clash Royale official API, full clan profile for a clan tag: name, description, type, score, member count, trophies required, and war trophies.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes

Output Schema

NameRequiredDescriptionDefault
tagNoClan tag identifier
nameNoClan name
typeNoClan type
badgeIdNoBadge ID
membersNoClan members list
locationNoClan location
clanScoreNoClan score
descriptionNoClan description
memberCountNoNumber of members
clanChestStatusNoClan chest status
clanWarTrophiesNoClan war trophies
donationsPerWeekNoDonations per week
requiredTrophiesNoRequired trophies to join

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile needs no restating. The description contributes that this is the official Clash Royale API and defines the scope of the payload, but says nothing about rate limits, auth/API-token requirements, behavior for invalid or unknown clan tags, or whether the tag must be URL-encoded — the practical failure modes for this call.

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 that identifies the API, the operation, the input, and the payload. The field enumeration is informative rather than padding, though it partly duplicates what the output schema already declares.

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 one-parameter read tool with rich annotations and a published output schema, the description covers purpose, source, and scope, so an agent can call it correctly. The remaining gap is the tag format convention, which is the one detail most likely to cause a failed invocation.

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?

Schema description coverage is 0%, so the description must carry the parameter burden, and it does so only partially: 'for a clan tag' tells the agent what the lone parameter means. It does not state the required tag format (leading '#', URL-encoding, no spaces), which the schema only hints at via an example value. Adequate but thin for a 0%-documented parameter.

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 names a specific resource ('full clan profile') and a specific selector ('for a clan tag'), then enumerates the returned fields (name, description, type, score, member count, trophies required, war trophies). That is clearly distinguishable from clash_royale_player or clash_royale_clan_members, though it never explicitly contrasts itself with clan_current_war or clan_war_log, which are the closest potential confusions.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent must infer from the phrase 'full clan profile' that this is the identity/summary call rather than the war, war-log, or search calls. Implied usage only, with nothing that routes the agent deliberately.

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.