Skip to main content
Glama
Sign In

CARDZ MCP

by io.github.cardzgame
OverviewDiscussionsAdmin

Search TCG cards

search_cards
Read-onlyIdempotent

Use this when the user names a card, set, or collector number and wants to find matching printings or get card IDs for further lookup. Searches CARDZ public graded Pokémon or One Piece cards. Returns candidate printings with names, sets, languages, market ranks, PSA 10 prices, populations, market caps, and canonical card links. Multiple candidates may match; call get_card with the exact id for full metrics. An empty result means no published match.

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": {
      "q": "<q>"
    },
    "name": "search_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCard name or collector number. Examples: 'Charizard', '199/165', 'OP05-119', 'Van Gogh Pikachu'. At least one meaningful keyword.
tcgNoOptional: 'pokemon' or 'one-piece'. Omit to search both games.
langNoLanguage for display labels in the response. Does not filter by card language; use tcg to narrow by game. Printing language is always returned in the result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Display language; printing language is returned separately."New value: +"Language for display labels in the response. Does not filter by card language; use tcg to narrow by game. Printing language is always returned in the result."
    • changedInput schema / properties / q / description
      Previous value: -"Card name or collector number, for example OP05-119 or 217/187."New value: +"Card name or collector number. Examples: 'Charizard', '199/165', 'OP05-119', 'Van Gogh Pikachu'. At least one meaningful keyword."
    • changedInput schema / properties / tcg / description
      Previous value: -"Optional game filter."New value: +"Optional: 'pokemon' or 'one-piece'. Omit to search both games."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description correctly focuses on what annotations cannot say: multiple candidates may match, the exact payload fields returned (PSA 10 prices, populations, market caps, canonical links), and that an empty result means no published match. It stops short of stating result limits or pagination behavior.

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?

Four sentences, each doing distinct work: trigger, scope, return payload, prerequisite for follow-up, and empty-result semantics. The when-to-use clause is front-loaded and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by enumerating the return fields and the empty-result meaning. Combined with annotations covering the safety profile and a fully documented 3-param schema, an agent has everything needed to call this correctly and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already explains q formats, the tcg enum, and the subtle 'lang does not filter printing language' caveat. The description's mention of names, sets, and collector numbers merely restates schema content, so baseline 3 applies.

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?

States a specific verb (search) and resource (CARDZ public graded Pokémon or One Piece cards), plus the trigger condition (user names a card, set, or collector number). It also explicitly contrasts with the sibling get_card, which handles exact-ID lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the when-to-use condition up front and names the alternative route: 'call get_card with the exact id for full metrics.' The two-step workflow (search then get_card) is spelled out, leaving no ambiguity about which tool to pick.

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

All CARDZ MCP 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