Skip to main content
Glama

Best Clash Royale decks right now

top_decks
Read-onlyIdempotent

The most played or highest win-rate Clash Royale decks from recent real battles of top players, with usage and win rate. Use for "best deck", "meta decks", "best Hog Rider deck", "decks without Mega Knight" and similar questions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "top_decks"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many recent days of battles to count.
modeNoGame mode. pathOfLegend is ranked.all
sortNoMost played, or highest win rate (decks with enough games only).usage
limitNo
scopeNoWhose games to count: top100 / top1000 ranked Path of Legends players (default), or all tracked players.top1000
exclude_cardsNoCard names no deck may contain.
include_cardsNoCard names every deck must contain, e.g. ["Hog Rider"].
archetype_familyNoDeck style to filter on.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description adds useful provenance (aggregated from recent real battles of top players) and a caveat that win-rate sorting only counts decks with enough games. It does not mention freshness lag, sample sizes, or that results are aggregates rather than a single deck list.

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?

Two sentences, zero filler: the first sentence front-loads what the tool returns and its data source, the second lists usage triggers. Nothing is repeated from the schema and every clause earns its place.

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 an 8-parameter, all-optional aggregation tool with 88% schema coverage and no output schema, the description covers data source, ranking semantics, and when to reach for it. The only real gap is a hint at the shape of the result (per-deck usage/win-rate entries) and whether results are cached or time-lagged.

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 88%, so the baseline is 3 and the schema already documents each parameter including an example for include_cards. The description's example queries do reinforce the include/exclude-card pattern ("decks without Mega Knight", "best Hog Rider deck"), adding a bit of practical framing, but it says nothing about days, scope, or archetype_family beyond what the schema states.

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 (Clash Royale decks) plus the ranking basis (most played or highest win-rate) and the data source (recent real battles of top players). It is clear what the tool returns, but it never contrasts itself with siblings like meta_snapshot or check_deck, so an agent must infer the boundary.

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?

Gives concrete when-to-use triggers via example phrasings ("best deck", "meta decks", "best Hog Rider deck", "decks without Mega Knight"), which map naturally onto the sort/include/exclude parameters. It stops short of stating when NOT to use it or naming check_deck/meta_snapshot as alternatives for narrower or broader needs.

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