Skip to main content
Glama

get_card_rulings

Retrieve official One Piece Card Game FAQs, errata, and judge rulings for a canonical card ID, ranked by authority and date, with optional inclusion of superseded rulings.

Instructions

Retrieve official FAQs, errata, and judge rulings linked to a canonical card_id (e.g. 'OP05-119'), ordered by authority ASC (1 highest .. 4 lowest), judge_tier (tier_0 > tier_2 > tier_1), then date DESC. Excludes superseded rulings by default unless include_superseded=True.

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": {
      "card_id": "<card_id>"
    },
    "name": "get_card_rulings"
  }
}

Input Schema

NameRequiredDescriptionDefault
card_idYes
include_supersededNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses the ordering semantics plus the default exclusion of superseded rulings. It does not mention auth or rate limits, but the output schema covers return values.

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?

The description is a single dense sentence that front-loads purpose and then adds ordering and filtering details. Every clause earns its place, and there is no filler.

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 two-parameter read retrieval tool with an output schema, the description covers scope, ordering, and the superseded default. It is complete enough to call correctly, though sibling routing guidance is 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?

Schema description coverage is 0%, so the description must compensate. It provides a concrete card_id example and explains the include_superseded default and effect, though it does not fully document format constraints on card_id.

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 uses a specific verb, 'Retrieve', and names the resources: official FAQs, errata, and judge rulings. It clearly scopes results to a canonical card_id, but does not explicitly contrast this tool with siblings such as get_card or search.

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 description implies usage when rulings are needed for a known canonical card_id and explains the include_superseded toggle. However, it gives no explicit when-to-use versus alternatives or when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.