Skip to main content
Glama

Record a purchase

record_purchase
Idempotent

Records a card the user bought to their SlabLineage collection with the price actually paid, on the Deal Desk session. Before calling, ask the user "Record bought for $?" and pass confirm true after they say yes. Give dealId from check_deal (preferred) or the same card fields as check_deal; for a slab pass certNumber read off the label when visible; quantity is for raw cards. PSA and TAG slabs with a cert SlabLineage can check go in the collection; other slabs are logged in Deal Desk without joining the collection (the pc.message says which). Pass an idempotencyKey so a retry never records twice. When the result has a nextLine (offering to list the card for sale), ask it. Where the assistant shows panels, the result opens a photo panel where the user can take the card's photo for the listing. If the result has alerts, show them to the user before anything else.

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": {
      "pricePaid": "<pricePaid>",
      "confirm": "<confirm>"
    },
    "name": "record_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoDefault pokemon.
gradeNoThe grade on the slab label, e.g. "10" or "9.5". Not needed for RAW.
cardIdNoSlabLineage card id from search_cards (any row of the card). Give cardId or the catalog id; one of them is required.
dealIdNoThe dealId from check_deal.
graderNoWithout dealId: the grading company on the label (PSA, TAG, CGC, BGS …) or RAW.
confirmYesTrue once the user said yes to recording this purchase; never set it before that.
quantityNoRaw cards: how many (default 1).
pricePaidYesThe price the user actually paid in USD (the total for the quantity).
certNumberNoThe cert number on the slab label, when visible.
scrydexCardIdNoOr the card's catalog id, e.g. "sv3pt5-199" (when you have it instead of cardId).
idempotencyKeyNoA unique key for this record (any short text you make up once); a retry with the same key never records twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare non-read-only, idempotent, non-destructive, but the description adds substantial context: the mandatory user confirmation, the idempotencyKey retry guarantee, the slab routing outcome, and follow-up behaviors (nextLine listing offer, photo panel, alerts to show first). This is well beyond what the annotations convey.

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?

Dense but front-loaded, starting with the core action and confirmation requirement before edge cases. It is a long single paragraph, but nearly every sentence carries operational guidance; minor tightening could improve scannability.

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 an 11-parameter mutation tool with no output schema, the description covers the confirmation flow, parameter selection strategy, slab routing, and how to interpret result fields (pc.message, nextLine, alerts, photo panel). An agent has what it needs to call and follow up correctly.

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%, so the baseline is 3, but the description adds real meaning: dealId is preferred over card fields, certNumber is read off the label when visible, quantity applies only to raw cards, and idempotencyKey prevents double-recording on retry. It does not explain every parameter, but it enriches the key ones.

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?

States a specific verb and resource ('Records a card the user bought to their SlabLineage collection') with the price actually paid and the Deal Desk session scope. This clearly distinguishes it from siblings like record_trade and undo_purchase.

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?

Explicitly says to prefer dealId from check_deal, or otherwise pass the same card fields as check_deal, and to ask a confirmation question before calling with confirm true. It also routes slab handling: PSA/TAG with a checkable cert join the collection, other slabs are only logged in Deal Desk.

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