SpellBook Finance

spellbook_inventory_holdings

Read-onlyIdempotent

Read one page of what a seller's own workspace holds, aggregated to one row per printing, finish and condition. Each row carries card name, set code, collector number, variant label, quantity owned, quantity available, the current unit market price and the resolved minimum-sell floor with the tier that produced it. Call this to answer what is in the collection, what it is worth, what is already listed versus still available, and which rows sit near their floor. It reports holdings; it does not rank them, pick what to sell, or state a listing's live marketplace status.

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>"
    },
    "name": "spellbook_inventory_holdings"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum rows to return, 1 to 500. Omit for the default of 100.
`cursor`	No	Opaque cursor from a previous page, passed back unchanged. Omit to start from the first page.
`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.
`workspaceId`	Yes	The workspace to read holdings for. Required.

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"
+}

First observedSep 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real value beyond them: it discloses the pagination model ('one page'), the row grain, and the exact per-row payload including the floor and the tier that produced it. It does not discuss continuation mechanics or ordering guarantees, so it is not fully exhaustive.

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?

Four short sentences, front-loaded with the definition, then the row shape, then the use cases, then the exclusions. The field enumeration is dense but each item maps to an actual returned column, so nothing is 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?

There is no output schema, so the description takes on the burden of describing return values and does so concretely (card name, set code, collector number, variant, owned vs available quantity, market price, floor plus tier). Combined with the stated exclusions, an agent has enough to call this correctly and interpret the results.

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 limit, cursor, context and workspaceId are already fully documented. The description only adds that the scope is the seller's own workspace, with no extra meaning for limit/cursor beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 plus the aggregation grain: 'Read one page of what a seller's own workspace holds, aggregated to one row per printing, finish and condition.' The closing sentence explicitly fences off adjacent capabilities (ranking, sell-picking, live listing status), which is what separates this from screener/movers/marketplace-listing siblings.

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 concrete trigger questions ('what is in the collection, what it is worth, what is already listed versus still available, which rows sit near their floor') and states what it is not for. It stops short of naming the alternative tool an agent should call when it needs ranking or sell decisions, so the routing is implied rather than explicit.

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?