Skip to main content
Glama

Search

search
Read-onlyIdempotent

Use this to look up trading cards or sealed products (Pokemon, One Piece, Disney Lorcana, Riftbound, Yu-Gi-Oh, Gundam and Dragon Ball Super Fusion World) by name. Returns up to 10 matches with ids to pass to fetch.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesCard or sealed product name.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query / description
      Added value: +"Card or sealed product name."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two genuinely new facts — results are capped at 10 and the returned ids are meant for `fetch`. That is useful, but it says nothing about no-match behavior or what a match record contains, keeping it at an adequate rather than rich level.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, the purpose stated first and the return/chaining detail second, with the franchise list folded inline rather than as a separate clause. Nothing is padding, though the long parenthetical product-line enumeration is the one part that could be trimmed or moved.

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 no explanation, and the description still supplies the two things the schema cannot: the 10-result cap and the hand-off to `fetch`. Only the absence of guidance on empty results keeps it from being fully complete for a one-parameter search tool.

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 coverage is 100% on the single `query` parameter, which is already documented as 'Card or sealed product name', so the baseline is 3. The description reinforces that the query is a name and that sealed products are included, but adds no syntax guidance such as set codes, partial matching, or fuzzy versus exact behavior.

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?

Specific verb and resource: 'look up trading cards or sealed products ... by name', with the supported product lines (Pokemon, One Piece, Lorcana, etc.) enumerated so the agent knows the domain scope. It falls short of a 5 because the closely-named sibling `search_cards` is never distinguished from this tool, leaving the boundary between the two ambiguous.

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 a clear usage path: look up by name, then take the returned ids to `fetch` for details — an explicit workflow chain rather than implied usage. It never says when this tool should not be used or why one would pick it over `search_cards`, so the main sibling-selection question is unanswered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources