Skip to main content
Glama

Ygoprodeck

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Cards

search_cards
Read-onlyIdempotent

Search Yu-Gi-Oh! trading card game (TCG) cards by name (fuzzy), card type, attribute, monster race/type, archetype, or level. Returns matching cards with names, types, descriptions, ATK/DEF, attributes, archetypes, images, and TCGplayer card prices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numNoNumber of results to return (default 20, max 50).
nameNoFuzzy card name match, e.g. "Dark Magician", "Blue-Eyes".
raceNoMonster type/race, e.g. 'Spellcaster', 'Dragon', 'Warrior'. For Spell/Trap, the property e.g. 'Continuous', 'Quick-Play'.
typeNoCard type, e.g. 'Effect Monster', 'Normal Monster', 'Spell Card', 'Trap Card', 'XYZ Monster'.
levelNoMonster level/rank, e.g. 7.
offsetNoPagination offset (default 0).
archetypeNoCard archetype, e.g. "Blue-Eyes", "Dark Magician", "Sky Striker".
attributeNoMonster attribute, e.g. 'DARK', 'LIGHT', 'EARTH', 'WATER', 'FIRE', 'WIND', 'DIVINE'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "name": "Dark Magician",
+    "num": 10,
+    "type": "Effect Monster"
+  },
+  {
+    "archetype": "Blue-Eyes",
+    "attribute": "LIGHT",
+    "level": 8,
+    "num": 20
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare safe, read-only, and idempotent behavior. The description adds value by specifying fuzzy name matching and the full set of returned fields, providing behavioral context beyond annotations.

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, front-loaded with purpose and filters, followed by output. No wasted words, highly efficient.

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?

The description covers filter options and output fields. Minor omissions like pagination and sorting are acceptable given no output schema and the tool's search nature.

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 has 100% description coverage, baseline 3. The description adds extra meaning (e.g., 'fuzzy' for name, 'monster type/race' for race), improving parameter understanding without redundancy.

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 clearly states the action ('Search'), the resource ('Yu-Gi-Oh! TCG cards'), and the filter criteria (name, type, attribute, etc.). It also lists output fields, distinguishing it from siblings like 'get_card' and 'random_card'.

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 for multi-criteria card search but does not explicitly state when to use it versus alternatives or mention exclusion criteria. Sibling tools include 'get_card' and 'random_card', but no direct comparison is made.

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

All Ygoprodeck toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources