Clash Royale

Tournament

tournament

Read-onlyIdempotent

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tag`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Tournament tag
`name`	No	Tournament name
`type`	No	Tournament type
`status`	No	Tournament status
`members`	No	Current member count
`capacity`	No	Maximum participants
`standings`	No	Tournament standings
`creatorTag`	No	Creator player tag
`maxPlayers`	No	Max players allowed
`createdTime`	No	Creation timestamp
`description`	No	Tournament description
`startedTime`	No	Start timestamp
`finishedTime`	No	End timestamp

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "tag": "#2PPGY2J9Q"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "capacity": {
+      "description": "Maximum participants",
+      "type": "number"
+    },
+    "createdTime": {
+      "description": "Creation timestamp",
+      "type": "string"
+    },
+    "creatorTag": {
+      "description": "Creator player tag",
+      "type": "string"
+    },
+    "description": {
+      "description": "Tournament description",
+      "type": "string"
+    },
+    "finishedTime": {
+      "description": "End timestamp",
+      "type": "string"
+    },
+    "maxPlayers": {
+      "description": "Max players allowed",
+      "type": "number"
+    },
+    "members": {
+      "description": "Current member count",
+      "type": "number"
+    },
+    "name": {
+      "description": "Tournament name",
+      "type": "string"
+    },
+    "standings": {
+      "description": "Tournament standings",
+      "type": "array"
+    },
+    "startedTime": {
+      "description": "Start timestamp",
+      "type": "string"
+    },
+    "status": {
+      "description": "Tournament status",
+      "type": "string"
+    },
+    "tag": {
+      "description": "Tournament tag",
+      "type": "string"
+    },
+    "type": {
+      "description": "Tournament type",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, read-only operation. The description adds the list of returned fields but does not disclose additional behavioral traits such as error handling, rate limits, or authentication requirements. With annotations covering the safety profile, the description adds moderate value but not rich behavioral context.

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?

The description is a single, well-structured sentence that front-loads the source (Clash Royale official API) and the purpose. Every word earns its place, with no redundancy or filler.

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?

The tool is simple with one parameter and has an output schema, so the description does not need to detail return values. It covers the resource and the fields contained in the result. It is slightly incomplete in that it does not mention when to use tournament_search or any error cases, but for a straightforward lookup tool, the description is adequate.

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 compensate. It mentions 'for a tournament tag' which clarifies the sole parameter 'tag', but it does not specify the tag format (e.g., with or without '#') beyond what the example in the schema shows. The description adds some meaning but leaves details to the schema example, so a baseline of 3 is appropriate.

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 provides tournament details for a specific tournament tag, listing the exact fields returned (name, description, max capacity, creator, current members, status, game mode). It uses a specific verb+resource structure and distinguishes from the sibling 'tournament_search' by focusing on a single tag rather than searching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes clear that this tool is used with a tournament tag, which is a specific context. However, it does not explicitly state when to use this instead of alternatives like 'tournament_search', nor does it mention any exclusions. The context is clear but lacks explicit alternative guidance.

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

All Clash Royale tools Inspect

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.