Skip to main content
Glama

Clash Royale Tournament

clash_royale_tournament
Read-onlyIdempotent

Clash Royale official API, tournament details for a tournament tag: name, description, max capacity, creator, current members, status, and game mode.

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": "#2PPGY2J9Q"
    },
    "name": "clash_royale_tournament"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes

Output Schema

NameRequiredDescriptionDefault
tagNoTournament tag
nameNoTournament name
typeNoTournament type
statusNoTournament status
membersNoCurrent member count
capacityNoMaximum participants
standingsNoTournament standings
creatorTagNoCreator player tag
maxPlayersNoMax players allowed
createdTimeNoCreation timestamp
descriptionNoTournament description
startedTimeNoStart timestamp
finishedTimeNoEnd timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and idempotency profile is fully covered. The description adds no behavioral context beyond that — no auth/API-key requirement, rate-limit behavior, error semantics for unknown tags, or caching — and its field enumeration is redundant with the existing output schema.

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 resource, the lookup key, and the returned fields with no filler. The only inefficiency is the field list, which duplicates what the output schema already provides.

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?

For a simple one-parameter read tool with annotations and an output schema, most of the burden is already handled by structured fields, and the description correctly covers identity and scope. What is missing is tag-format guidance and the relationship to tournament_search, which are the realistic failure modes for this call.

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 tag's meaning; it does identify the parameter as a tournament tag, which is useful. However, it omits format specifics that matter for this API (leading '#', URL-encoding of '#', tag case), leaving the agent to infer from the schema example alone.

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 the resource concretely ('tournament details for a tournament tag') and enumerates the substantive fields returned (name, description, max capacity, creator, members, status, game mode), so an agent can tell this is a single-tournament lookup rather than a listing. It stops short of naming or contrasting with the sibling tournament_search, which is the one plausible point of confusion.

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 explicit when-to-use or when-not-to-use guidance. The phrase 'for a tournament tag' implies the precondition of already holding a tag, but the description never says to use tournament_search when the tag is unknown, nor what happens with an invalid or malformed tag.

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.