Skip to main content
Glama

Card prices

get_card_price
Read-onlyIdempotent

The stored prices shown on a SlabLineage card page: the SL Consensus price and the PSA / TAG market prices across grades, with the same labels the page uses. Values are USD. The card page's raw (ungraded) price is returned separately as raw, or null when the page shows none.

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": {
      "cardId": "<cardId>"
    },
    "name": "get_card_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYesSlabLineage card id (the number in https://slablineage.com/card/{id}).

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 read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower and the description usefully adds that values are USD, that labels mirror the page, and that the raw ungraded price is returned separately with null when absent. That null semantics is genuine behavioral context an agent needs. It stops short of saying what happens for an unknown card id or an empty price set.

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?

Three tight sentences, front-loaded with what is returned, then the field labeling, then the unit and the raw/null edge case. No filler or restatement of the title.

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 carries the return-value burden and does reasonably well: it lists the price categories, the grade dimension, the currency, and the raw/null case. The remaining gap is the response's actual shape and handling of cards with no stored prices, which the agent would still have to discover.

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% for the single cardId parameter, and the description adds nothing beyond the schema's own note about the SlabLineage card id format. The baseline of 3 applies when the schema already carries the parameter meaning.

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?

The description names a specific resource — the stored prices on a SlabLineage card page, itemized as SL Consensus and PSA/TAG market prices across grades. It is clear what the tool returns, though the verb is implicit (the name supplies 'get') and no sibling such as get_price_history is named to sharpen the boundary.

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?

The phrase 'The stored prices shown on a SlabLineage card page' implies a current snapshot rather than a historical series, which quietly distinguishes it from get_price_history without saying so explicitly. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer the choice.

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