Skip to main content
Glama

get_card

Use this for any question about one catalog card once you already have its id. It returns the name, set, collector number, image, language (en or ja), and rarity for Pokémon (English and Japanese), Magic: The Gathering, Yu-Gi-Oh!, One Piece, and Riftbound. Unknown language or rarity is null, and it does not return prices or PSA population. Free, limited to 60 per minute and 1000 per key per UTC day, shared with the other free catalog calls.

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": {
      "card_id": "<card_id>"
    },
    "name": "get_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
card_idYesCatalog card UUID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / card_id / format
      Added value: +"uuid"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral load well: it discloses free-tier rate limits (60/min, 1000 per key per UTC day, pooled across other free catalog calls) and the null semantics for unknown language or rarity. It does not describe failure behavior for an invalid or non-existent id, which is the main remaining gap.

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?

Front-loaded with the use case and packed with actionable detail — rate limits, null handling, and exclusions — in only a few sentences. The enumeration of return fields is partly redundant with the existing output schema, a small amount of repeated information.

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?

For a one-parameter lookup with a full output schema and no annotations, this covers everything an agent needs: when it applies, what it returns, which games are supported, what null means, what is deliberately absent, and the cost/throughput ceiling. Nothing material is missing.

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?

The single card_id parameter is already 100% documented in the schema as a UUID, so the baseline would be 3; the description adds the constraint that an id must be obtained beforehand, which clarifies the provenance and format expectation beyond the schema text.

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 states a specific verb and resource (retrieve one catalog card by id) plus the exact field set returned and the game lines covered (Pokémon EN/JA, MTG, Yu-Gi-Oh!, One Piece, Riftbound). Paired with the precondition 'once you already have its id', an agent can distinguish this from find_card/search_cards without opening any schema.

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?

It gives a clear precondition ('once you already have its id') and explicit content exclusions: no prices, no PSA population — effectively routing price and population questions elsewhere. It stops short of naming those alternative tools or stating what to do when the id is unknown, so it is strong but not fully prescriptive.

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