Skip to main content
Glama

A player's Clash Royale practice priorities

player_practice_priorities
Read-onlyIdempotent

For a player tag (e.g. #8Q2V0CJL): their record, decks, and up to three matchups to practice, comparing their win rate with similar players in the same matchup. Only works for players Insights Royale already tracks; otherwise returns a link to start tracking.

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": {
      "player_tag": "<player_tag>"
    },
    "name": "player_practice_priorities"
  }
}

Input Schema

NameRequiredDescriptionDefault
player_tagYesThe in-game player tag, with or without #.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 is covered. The description adds real value beyond that: it caps results at three matchups, explains the win-rate comparison against similar players, and discloses the untracked-player fallback of returning a tracking link instead of data.

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?

Two tightly written sentences, with the primary output scope front-loaded and the eligibility caveat second. Nothing is redundant, though the parenthetical example tag is slightly gratuitous given the schema.

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?

There is no output schema, so the description must carry the return-value burden, and it does: record, decks, candidate matchups, comparative win rate, and the fallback link. A one-param read-only tool needs little more, though the exact shape of the 'record' and matchup entries remains unstated.

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 coverage is 100% with a single documented player_tag parameter that already states '#' is optional. The description adds only an example tag value, which is mildly helpful but restates what the schema provides, 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 names the resource (a player's record, decks, and up to three practice matchups) and the comparison it performs against similar players. It is clearly distinguishable from check_deck, meta_snapshot, and top_decks, which operate on decks/meta rather than a specific player tag, though it never explicitly contrasts itself with them.

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 only guidance is a prerequisite/eligibility rule: it works only for players already tracked by Insights Royale and otherwise returns a tracking link. That is useful context, but there is no explicit when-to-use guidance and no named alternative for the untracked-player case.

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