Skip to main content
Glama

RipSeek

One card in detail

get_card
Read-onlyIdempotent

Shows one Rare or Epic card that is in a pack pool right now: name, insured value, picture, and every pack it can come from with that pack's price and the chance per pack of pulling this exact card. Use it after search_cards, passing the nft field of a result; use search_cards when you only have a card name. Read-only; fails with a clear message if the card has just been pulled and left the pool.

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

Input Schema

NameRequiredDescriptionDefault
nftYesThe card's NFT address (Solana, base58) from a search_cards result, e.g. 7xKX...q9Fz.

Output Schema

NameRequiredDescriptionDefault
nftNo
cardYes
noteNo
imageNo
packsYes
value_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/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, open-world behavior, so the safety profile is covered. The description still adds value beyond them by disclosing a volatility edge case: the call fails with a clear message if the card was just pulled and left the pool. It does not mention rate limits or pagination, but neither appears relevant for a single-entity lookup.

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?

The definition is three compact clauses with no filler, and the core purpose is front-loaded before usage routing and the failure caveat. The first sentence is dense with parallel list items, but each item is a distinct returned field rather than padding.

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 single-entity read with an output schema already describing return values, the description supplies everything else an agent needs: input provenance, the sibling to use instead, and the one runtime failure mode. Nothing required for a correct call 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?

Schema coverage is 100% and the schema already explains the base58 Solana address format, so the baseline is 3. The description goes further by tying the parameter to its provenance ("the nft field of a result" from search_cards), telling the agent where the value must come from rather than just its type.

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 opens with a specific verb and resource ("Shows one Rare or Epic card") and enumerates exactly what is returned: name, insured value, picture, and every eligible pack with its price and pull chance. It also scopes the resource to cards currently in a pack pool, which distinguishes it from the sibling search tool.

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?

It states the precise sequence ("Use it after search_cards, passing the nft field of a result") and names the alternative condition explicitly ("use search_cards when you only have a card name"). That is an explicit when-to-use plus when-to-use-something-else, leaving nothing to inference.

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