Skip to main content
Glama

Clash Royale meta snapshot

meta_snapshot
Read-onlyIdempotent

The current Clash Royale meta from real battles: how popular each deck style is, which styles beat which, and the cards rising or falling in use.

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

Input Schema

NameRequiredDescriptionDefault
modeNoGame mode. pathOfLegend is ranked.all
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.6/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 ('from real battles') and recency ('current'), but says nothing about the time window covered, aggregation method, or response shape.

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 sentence, front-loaded with the core concept and then enumerating the three returned signals. No filler, no repetition of the title, and nothing that could be cut without losing information.

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 must convey what comes back, and it does so by naming three result categories. It falls slightly short on defining the 'current' time window and on how 'rising or falling' is measured, which matters for interpreting results.

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 100% and both parameters carry enums with inline descriptions, including the note that pathOfLegend is ranked. The description adds no extra meaning about mode or scope beyond what the schema already supplies, so the baseline of 3 applies.

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 resource and content set: current meta popularity by deck style, style-vs-style matchups, and card usage trends. It is concrete enough that an agent can distinguish it from a deck-listing tool like top_decks, though it never explicitly names or contrasts with any sibling.

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 by the words 'current' and 'meta' — an agent can infer this is for trend/aggregate questions rather than single-deck lookups. There is no explicit when-to-use, when-not-to-use, or routing to alternatives such as check_deck or top_decks.

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