Skip to main content
Glama

search_cards

Filter canonical One Piece Card Game cards by name, color, cost, trait, keyword, or set code to locate specific cards for deck building or rules lookup.

Instructions

Filter canonical OPTCG cards by name substring, color, exact cost, trait substring, effect/trigger keyword (e.g. '[Blocker]' or 'Rush'), and set_code (e.g. 'OP05'). Defaults to returning up to 25 matches (max 100).

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

Input Schema

NameRequiredDescriptionDefault
costNo
nameNo
colorNo
limitNo
traitNo
keywordNo
set_codeNo

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 at all, the description carries the full burden, and it does disclose key runtime behavior: a default result cap of 25 and a hard maximum of 100, which tells the agent how to size queries and why results may be truncated. It omits sort order, case sensitivity, and empty-result behavior, but the pagination disclosure is the higher-value piece.

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 verb and resource, then the filter modes, ending with the limit behavior. Every clause carries information and nothing is restated from the title or schema titles.

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?

An output schema exists, so return values need not be explained, and all 7 parameters get some coverage in prose. The remaining gap is discoverability of legal values for free-text fields like color and keyword, which an agent cannot infer without an enum or a pointer to a reference tool.

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% across 7 parameters, so the description must compensate and largely does: it specifies matching semantics per field (name SUBSTRING, trait SUBSTRING, cost EXACT, set_code example 'OP05', keyword example '[Blocker]' or 'Rush') and covers the limit parameter via the 25 default / 100 max. It does not give valid color values or state case-sensitivity, which matters since no parameter has an enum.

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 a specific verb (filter) and resource (canonical OPTCG cards) and enumerates the filterable fields, so the agent knows exactly what the tool returns a subset of. It falls short of a 5 only because it never names the obvious sibling (get_card) to draw the boundary between bulk search and single-card lookup.

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 by the filter list: use it when you have partial attributes (substring name, color, cost, trait, keyword, set_code) rather than a known card ID. There is no explicit when-not guidance, no mention of get_card as the alternative for a single known card, and no statement about what to do when zero filters are supplied.

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