Skip to main content
Glama

Cards

cards
Read-onlyIdempotent

Clash Royale official API, complete list of all game cards: name, max level, elixir cost, rarity, type, arena, and icon URL.

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": "cards"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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: +[
      +  {}
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Number of items returned.",
      +      "type": "integer"
      +    },
      +    "items": {
      +      "items": {
      +        "properties": {
      +          "arena": {
      +            "description": "Arena unlock level",
      +            "type": "number"
      +          },
      +          "description": {
      +            "description": "Card description",
      +            "type": "string"
      +          },
      +          "elixirCost": {
      +            "description": "Elixir cost",
      +            "type": "number"
      +          },
      +          "iconUrls": {
      +            "description": "Icon URLs",
      +            "type": "object"
      +          },
      +          "id": {
      +            "description": "Card ID",
      +            "type": "number"
      +          },
      +          "key": {
      +            "description": "Card key identifier",
      +            "type": "string"
      +          },
      +          "maxLevel": {
      +            "description": "Maximum card level",
      +            "type": "number"
      +          },
      +          "name": {
      +            "description": "Card name",
      +            "type": "string"
      +          },
      +          "rarity": {
      +            "description": "Card rarity",
      +            "type": "string"
      +          },
      +          "type": {
      +            "description": "Card type",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "items",
      +    "count"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, covering the safety profile. The description adds that the data comes from the 'official API' (implying an authoritative, static reference list), but says nothing about freshness, caching, or pagination.

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?

A single front-loaded sentence that names the source first and then the payload fields, with no wasted wording. Nothing is buried or repeated.

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?

For a zero-param reference-list tool with a full output schema and complete annotation coverage, the description supplies everything needed to call it correctly. Only minor operational details (data freshness/refresh cadence) are absent.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics to explain. The description correctly signals that the call is argument-free.

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 clear resource ('complete list of all game cards') and enumerates the returned fields, so the agent knows exactly what data comes back. It doesn't explicitly contrast itself with the clash_royale_player/clan siblings, but the resource is unambiguous on its own.

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 when-to-use guidance, no prerequisites, and no mention of alternatives for fetching card data. Usage is only inferable from the resource name, leaving the agent to guess whether a filtered or per-card lookup exists.

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.