Skip to main content
Glama

Log an in-person sale

log_sale
DestructiveIdempotent

Records an in-person sale of a card in the user's collection: a Deal Desk purchase (dealId), a cardId or a claimId, with the total sale price, quantity and any fees (venue show by default). Ask the user "Record sold for $?" and pass confirm true after they say yes. A card that sold online and isn't confirmed yet is refused. The card leaves the collection (its oldest cost lots are used) and the sale counts in today's Deal Desk numbers. 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": {
      "salePrice": "<salePrice>",
      "confirm": "<confirm>"
    },
    "name": "log_sale"
  }
}

Input Schema

NameRequiredDescriptionDefault
feesNoAny fees paid on this sale in USD (default 0).
venueNoWhere it sold (default show).
cardIdNoOr the card's SlabLineage id in the user's collection.
dealIdNoA Deal Desk purchase (from record_purchase).
claimIdNoOr the collection claim id.
confirmYesTrue once the user said yes to recording this sale; never set it before that.
quantityNoHow many were sold (default 1).
salePriceYesThe total sale price in USD.
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.5/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, openWorldHint=false, idempotentHint=true), the description discloses the actual side effects: the card leaves the collection using its oldest cost lots, the sale counts in today's Deal Desk numbers, unconfirmed online sales are rejected, and alerts must be shown. This is exactly the mutation context the annotations alone cannot 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?

Front-loaded with what is recorded and the identifiers, then the confirmation protocol, then side effects and refusal rule. A dense but efficient paragraph; the confirmation-dialogue wording and alerts instruction are load-bearing rather than filler.

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?

A destructive, multi-parameter write tool with no output schema, and the description covers side effects, refusal behavior, and how to handle returned alerts, which is most of what an agent needs. It is slightly thin on failure/error handling and on how to pick between dealId, cardId, and claimId when several are available.

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 tied to a Deal Desk purchase from record_purchase, venue defaults to show, salePrice is the total, and confirm must only be set after the user agrees. Identifier precedence among dealId/cardId/claimId is gestured at with 'or' but not fully disambiguated.

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 (records) plus resource (a sale of a card in the user's collection) and enumerates the three ways to identify the item (dealId, cardId, claimId), so it is clearly distinct from record_purchase and record_trade. The 'in-person sale' framing and the note that the card leaves the collection make the operation unmistakable.

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?

Gives a concrete pre-call workflow (ask "Record <card> sold for $<price>?" then pass confirm true) and a refusal condition (a card that sold online and is not yet confirmed is refused), plus post-call guidance to surface alerts first. It does not, however, contrast with siblings like my_sales, record_trade, or listing tools when different sale paths could apply.

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