Skip to main content
Glama

Clash Royale

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Tournament Search

tournament_search
Read-onlyIdempotent

Clash Royale official API — search open tournaments by name. Returns matching tournaments with capacity, current members, and start time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
afterNo
limitNo
beforeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoSearch results
pagingNoPagination info

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "name": "Grand Challenge"
+  },
+  {
+    "limit": 5,
+    "name": "Classic"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "description": "Search results",
+      "items": {
+        "properties": {
+          "capacity": {
+            "description": "Capacity",
+            "type": "number"
+          },
+          "createdTime": {
+            "description": "Created timestamp",
+            "type": "string"
+          },
+          "creatorTag": {
+            "description": "Creator tag",
+            "type": "string"
+          },
+          "finishedTime": {
+            "description": "Finished timestamp",
+            "type": "string"
+          },
+          "maxPlayers": {
+            "description": "Max players",
+            "type": "number"
+          },
+          "members": {
+            "description": "Member count",
+            "type": "number"
+          },
+          "name": {
+            "description": "Tournament name",
+            "type": "string"
+          },
+          "startedTime": {
+            "description": "Started timestamp",
+            "type": "string"
+          },
+          "status": {
+            "description": "Tournament status",
+            "type": "string"
+          },
+          "tag": {
+            "description": "Tournament tag",
+            "type": "string"
+          },
+          "type": {
+            "description": "Tournament type",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "paging": {
+      "description": "Pagination info",
+      "properties": {
+        "cursors": {
+          "description": "Pagination cursors",
+          "type": "object"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds value beyond annotations by specifying the return content ('capacity, current members, and start time') and the 'Clash Royale official API' source, which helps set expectations.

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, front-loaded sentence that concisely conveys the tool's purpose and return data. Every word earns its place with no redundancy.

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?

With an output schema present, the description need not explain return values. The tool is simple (no required parameters) and the description covers the core functionality. However, parameter semantics are weak, slightly reducing completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 for explaining the parameters. It only implies 'name' as the search term but does not clarify 'after', 'before', or 'limit'. This leaves three parameters unexplained.

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 verb 'search' and resource 'open tournaments by name', distinguishing it from sibling 'tournament' which likely fetches a specific tournament. It also specifies the API source and return fields.

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 provides clear context for when to use this tool: to search open tournaments by name. It does not explicitly mention alternatives or exclusions, but the context is unambiguous enough for an agent to select it over siblings.

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

All Clash Royale toolsInspect
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.

Resources