Skip to main content
Glama

Check a Clash Royale deck

check_deck
Read-onlyIdempotent

Rates an 8-card Clash Royale deck: role checks (win condition, spells, air defense…), how it and similar decks have done in real battles, its matchups against each deck style, and one-card swaps that won more. Write "Evo Knight" or "Knight (Hero)" for those slots.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cards": "<cards>"
    },
    "name": "check_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardsYesThe 8 card names.
scopeNoWhose games to count: top100 / top1000 ranked Path of Legends players (default), or all tracked players.top1000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, so the bar is lower. The description still adds useful behavior beyond them by disclosing the analysis dimensions returned (role checks, battle history, style matchups, upgrade suggestions), which matters since no output schema exists. It does not mention rate limits or latency, keeping it from a 5.

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?

A single dense sentence front-loads the verb and then enumerates the outputs, with the card-naming note appended where it is needed. Nothing is redundant, though the parenthetical list with an ellipsis is slightly loose.

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 no output schema, the description carries the return-value burden and does so by naming the four analysis components. Combined with full parameter coverage, an agent knows enough to call it correctly and interpret the result; only the scope parameter's practical effect is left to the schema.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds a genuinely useful naming convention for the cards array ("Evo Knight" or "Knight (Hero)") that the schema's bare "The 8 card names" does not supply. The scope parameter's meaning is left entirely to the schema.

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 verb+resource ("Rates an 8-card Clash Royale deck") and enumerates what the rating covers: role checks, real-battle performance, matchups by deck style, and one-card swaps. It does not differentiate itself from siblings like top_decks or meta_snapshot, so it stops short of a 5.

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 usage is only implied — an agent can infer you use this to evaluate a candidate deck, and the caveat about writing "Evo Knight" or "Knight (Hero)" implies evolution/hero slots exist. There is no explicit when-to-use, when-not-to-use, or named alternative among siblings.

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.

Resources