Skip to main content
Glama

get_rule

Retrieve a specific One Piece Card Game comprehensive rule by canonical rule_id, including its ancestor chain and optional descendant sub-rules for accurate rules lookup.

Instructions

Retrieve a specific OPTCG Comprehensive Rule by canonical rule_id (e.g. '7-1-4' or '7-1-4-1'), including its ancestor chain and, when include_children=True, all descendant sub-rules ordered numerically.

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": {
      "rule_id": "<rule_id>"
    },
    "name": "get_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_idYes
include_childrenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful beyond-schema behavior: the ancestor chain is always returned, descendants are included only when include_children=True, and children are ordered numerically. It stops short of stating that this is a read-only operation, the default value of include_children, or what happens for an invalid/unknown rule_id.

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?

One dense sentence, front-loaded with the retrieval action and key, then the payload semantics. Every clause (id format, ancestor chain, conditional children, ordering) carries information with 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 lookup with an output schema present, the definition covers what the agent must know to call it correctly and what the payload structure looks like. Minor gaps remain around error behavior for malformed ids and the conditional's default, but nothing essential is missing.

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, and it does: rule_id is explained as a canonical dotted id with format examples, and include_children is tied to a concrete effect (all descendant sub-rules, numerically ordered). It omits that include_children defaults to true, which the schema declares but the prose does not reinforce.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Retrieve a specific OPTCG Comprehensive Rule') and pins the lookup key to a 'canonical rule_id' with concrete examples ('7-1-4', '7-1-4-1'). That id-keyed lookup framing distinguishes it from the search/search_cards siblings without needing to name 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?

Usage is implied rather than stated: the agent must already possess a canonical rule_id to call this, and the include_children flag is explained, but there is no explicit 'use this instead of search when you have an id' routing or any exclusion. Adequate context, no guidance on alternatives.

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