SpellBook Finance

spellbook_sealed_listing_preview

Read-onlyIdempotent

Preview one sealed listing on ManaPool or TCGplayer without publishing. Returns the proposed quantity and ask, any current offer, TCG publisher readback state, stock and intent revisions, and blockers. For TCGplayer, the first call may queue an exact seller-grid SKU read; call again after the paired extension finishes. After submitting, call preview again: publisher.state live confirms an offer, and removed confirms a zero-quantity removal. Pass this preview's channel, ask, and revisions to spellbook_sealed_listing_submit.

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": {
      "workspaceId": "<workspaceId>",
      "boxId": "<boxId>",
      "kind": "<kind>"
    },
    "name": "spellbook_sealed_listing_preview"
  }
}

Input Schema

Name	Required	Description	Default
`cap`	No	The most units to offer at once. Omit to offer every eligible unit.
`game`	No	The game of the product. Defaults to mtg.	mtg
`kind`	Yes	The sealed kind, the kind on the same spellbook_sealed_portfolio row. Required, because units are counted by kind and boxId together.
`boxId`	Yes	The TCGplayer product id of the sealed product, the boxId on a spellbook_sealed_portfolio row. Required.
`channel`	No	Marketplace to preview. Defaults to manapool.	manapool
`context`	No	Optional analytics context: briefly describe the user's underlying goal in one sentence. Do not copy prompts, personal details, credentials, identifiers, or tool arguments. Omit for private tasks.
`floorUsd`	No	undercut only. The lowest ask in USD the rule may choose. Omit to use catalog market times floorMarketFraction.
`language`	No	The product language code, such as EN or JA. Defaults to EN.	EN
`takeover`	No	True adopts a listing on the selected marketplace that SpellBook did not create. Defaults to false; pass true only after the person agrees.
`priceRule`	No	market asks the catalog market price. undercut sets the ask so the item plus the seller's own shipping lands one cent under the cheapest TCGplayer item plus shipping from another seller, never below the floor. Omit for market.
`workspaceId`	Yes	The workspace that holds the sealed units, from spellbook_workspaces_list. Required.
`fixedPriceUsd`	No	A fixed ask in USD for every unit. Omit to list at the product's current market price. Cannot be combined with priceRule.
`floorMarketFraction`	No	undercut only. The floor as a fraction of catalog market, used when floorUsd is omitted. Defaults to 0.9.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Optional analytics context: briefly describe the user's underlying goal in one sentence. Do not copy prompts, personal details, credentials, identifiers, or tool arguments. Omit for private tasks.",
+  "maxLength": 512,
+  "type": "string"
+}

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / game / enum

Previous value: -[
-  "mtg",
-  "riftbound",
-  "pokemon"
-]New value: +[
+  "mtg",
+  "riftbound",
+  "pokemon",
+  "yugioh"
+]

Changed4 schema fields changedSep 30, 2026

changedInput schema / properties / fixedPriceUsd / description

Previous value: -"A fixed ask in USD for every unit. Omit to list at the product's current market price."New value: +"A fixed ask in USD for every unit. Omit to list at the product's current market price. Cannot be combined with priceRule."

addedInput schema / properties / floorMarketFraction

Added value: +{
+  "description": "undercut only. The floor as a fraction of catalog market, used when floorUsd is omitted. Defaults to 0.9.",
+  "exclusiveMinimum": 0,
+  "maximum": 1,
+  "type": "number"
+}

addedInput schema / properties / floorUsd

Added value: +{
+  "description": "undercut only. The lowest ask in USD the rule may choose. Omit to use catalog market times floorMarketFraction.",
+  "exclusiveMinimum": 0,
+  "maximum": 100000,
+  "type": "number"
+}

addedInput schema / properties / priceRule

Added value: +{
+  "description": "market asks the catalog market price. undercut sets the ask so the item plus the seller's own shipping lands one cent under the cheapest TCGplayer item plus shipping from another seller, never below the floor. Omit for market.",
+  "enum": [
+    "market",
+    "undercut"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedSep 27, 2026

addedInput schema / properties / channel

Added value: +{
+  "default": "manapool",
+  "description": "Marketplace to preview. Defaults to manapool.",
+  "enum": [
+    "manapool",
+    "tcgplayer"
+  ],
+  "type": "string"
+}

changedInput schema / properties / takeover / description

Previous value: -"True adopts a ManaPool listing for this product that SpellBook did not create. Defaults to false; pass true only after the person agrees."New value: +"True adopts a listing on the selected marketplace that SpellBook did not create. Defaults to false; pass true only after the person agrees."

AddedSep 25, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the return payload (quantity, ask, current offer, publisher readback state, blockers), the async two-call pattern for TCGplayer seller-grid SKU reads, and the meaning of publisher.state live/removed after submission. This is exactly the extra behavioral context annotations 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 the core purpose, then layered workflow detail; four sentences with little filler. The TCGplayer extension sentence is dense but earns its place by explaining an otherwise surprising two-call requirement.

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 13-parameter tool with no output schema, the description covers what is returned, the TCGplayer asynchronous readback loop, post-submit verification semantics, and the hand-off to submit. An agent has enough to call it and interpret results without further speculation.

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 description coverage is 100%, so every parameter including cap, priceRule, floorUsd, and takeover is already documented. The description only alludes to passing 'channel, ask, and revisions' to the submit tool and adds no syntax or constraint detail beyond the schema, so the baseline of 3 applies.

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, resource, and scope: preview one sealed listing on ManaPool or TCGplayer without publishing. It explicitly separates itself from the publishing step by naming spellbook_sealed_listing_submit as the follow-on tool, so an agent can distinguish intent without opening a 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?

Gives clear operational context: use it before submitting, call it again after the TCGplayer extension finishes, and re-run it after submit to verify publisher.state. It does not explicitly rule out or differentiate against adjacent preview tools (e.g. spellbook_tcg_listing_preview, marketplace_listings_adopt_preview), which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SpellBook Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?