Skip to main content
Glama

Search cards

search_cards
Read-onlyIdempotent

Find SlabLineage card pages by name, set or card number. Covers Pokémon and One Piece cards and PSA-graded sports slabs. Returns up to 12 cards, each with its card page URL and id.

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_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoLimit results to one game.
queryYesCard name, set name or card number, e.g. "charizard base set".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely new context: a hard result cap of 12 and the shape of each returned item (card page URL and id), which the annotations do not convey.

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 tight sentences: the first front-loads what is searched and over what scope, the second gives the result cap and return shape. No filler or redundancy.

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?

With no output schema, the description usefully compensates by stating the result count limit and per-item fields. For a simple two-parameter read tool this is nearly complete; only matching behavior (e.g. fuzzy vs exact) is left unstated.

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%, so both parameters are already documented, including the game enum and the query example. The description restates the query semantics ('by name, set or card number') without adding format or matching rules beyond the schema, so baseline 3 applies.

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 ('Find SlabLineage card pages') plus the searchable fields (name, set, card number) and the covered games. It is clear what the tool does, though it never names a sibling such as search_my_collection to draw the boundary between catalog search and collection search.

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 only implied: an agent can infer this is the catalog lookup tool, but there is no explicit when-to-use or when-not-to-use statement, and no pointer to alternatives like search_my_collection for personal holdings.

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