Skip to main content
Glama

get_card

Look up One Piece Card Game cards by canonical card ID or name, including exact or fuzzy matches, and return all matching printings and versions.

Instructions

Look up an OPTCG card by canonical card_id (e.g. 'OP05-119', 'ST10-001', 'P-001') or by name (exact or fuzzy, ignoring punctuation differences like 'Monkey D Luffy'). Returns all matching canonical card printings/versions.

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": {
      "id_or_name": "<id_or_name>"
    },
    "name": "get_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_or_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one important trait: a single lookup can return multiple canonical printings/versions, so callers should expect a list rather than one card. It does not state read-only nature explicitly, empty-result behavior, or any rate/permission constraints; the presence of an output schema covers the return 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?

Two sentences, no filler, with the primary lookup behavior front-loaded and the return behavior placed second. Every clause carries information an agent needs.

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 one-parameter lookup tool with an output schema, the definition covers input formats, matching behavior, and return multiplicity adequately. Only minor gaps remain: behavior on zero matches and how this differs from the sibling search_cards.

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 0% and the single parameter is entirely undocumented structurally, so the description must compensate — and it does, with concrete ID format examples ('OP05-119', 'ST10-001', 'P-001') and explicit fuzzy/exact name semantics including punctuation-insensitive matching ('Monkey D Luffy'). It stops short of saying how ties among multiple fuzzy matches are resolved, but the 'all matching' phrasing largely covers that.

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 verb and resource ('Look up an OPTCG card') and names the two lookup key types (card_id or name), so the agent knows exactly what the tool does. It does not explicitly contrast with the sibling search_cards, leaving a plausible overlap for the caller to resolve.

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 clear context for use: supply a canonical card_id or a name, exact or fuzzy. It does not state when to prefer this over search_cards or what to do if no match is found, but the input-driven context is unambiguous.

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