Skip to main content
Glama

Player Upcoming Chests

player_upcoming_chests
Read-onlyIdempotent

Clash Royale official API, upcoming chest cycle for a player tag: chest type and position index for the next chests in queue.

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": "#2P8888R"
    },
    "name": "player_upcoming_chests"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "tag": "#2P8888R"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Number of items returned.",
      +      "type": "integer"
      +    },
      +    "items": {
      +      "items": {
      +        "properties": {
      +          "index": {
      +            "description": "Position in chest queue",
      +            "type": "number"
      +          },
      +          "name": {
      +            "description": "Chest name",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "items",
      +    "count"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds only that this is the official API and roughly what the payload contains; it says nothing about rate limits, tag normalization, or what happens for an invalid/unknown tag.

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?

One front-loaded sentence that names the domain, the resource, and the return fields with no filler. It could be tightened slightly, but every clause carries information.

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?

An output schema exists, so explaining return values is not required, and the annotations cover safety. However, for a single-parameter tool with zero schema coverage, the definition leaves the tag format and error behavior unaddressed, which is the main residual gap.

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 single 'tag' parameter is undocumented structurally; the description partially compensates by stating it is a player tag, but it never specifies the required '#XXX' format or whether the leading hash is mandatory, leaving real ambiguity.

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?

States a specific resource (upcoming chest cycle) tied to a specific entity (a player tag) and enumerates the returned fields (chest type, position index). It is clear what the tool does, though it does not name a sibling tool or draw an explicit boundary against the player/clan endpoints.

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?

Usage is only implied: the agent can infer it is for fetching a player's future chest queue, but there is no statement of when to prefer it over clash_royale_player or other player endpoints, and no prerequisites such as tag format or that the player must exist.

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.