Skip to main content
Glama

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.

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": {
      "name": "Grand Challenge"
    },
    "name": "tournament_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
afterNo
limitNo
beforeNo

Output 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

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context by saying it returns matching tournaments with capacity, members, and start time, but it does not explain pagination behavior or limits related to the after/before/limit parameters.

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?

The description is two sentences and front-loads the core purpose. The second sentence is somewhat redundant because an output schema exists, but it still adds useful context about returned tournament fields and does not waste much space.

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?

The output schema reduces the need to explain return values, and annotations cover safety. However, with four input parameters at 0% schema coverage and no description of pagination or ordering, the definition is only minimally complete for a search tool.

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% for four parameters. The description only clarifies that search is by name, leaving after, before, and limit undocumented in both the schema and the description; the examples show limit but do not explain its semantics.

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 states a specific verb and resource: search open tournaments by name in the Clash Royale API. It is clear enough to distinguish this from a general tournament-detail tool, though it does not explicitly name or contrast with the sibling clash_royale_tournament.

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

Usage Guidelines3/5

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

The description implies the tool is used when looking for open tournaments by name, but it gives no explicit when-to-use guidance, prerequisites, or alternatives such as clash_royale_tournament. Usage is inferable but not well guided.

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.