SpellBook Finance

spellbook_ebay_pricing_restoration_prepare

Prepare a new exact eBay pricing approval from selected accepted source receipts. Returns eligible listing identities, typed conflicts and missing evidence. First read the source with spellbook_ebay_pricing_approval_get. The owner must choose manual automation and approve the new compensation in the web app; read its approval before spellbook_ebay_pricing_approval_execute.

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>",
      "sourceOperationId": "<sourceOperationId>",
      "listingIds": "<listingIds>"
    },
    "name": "spellbook_ebay_pricing_restoration_prepare"
  }
}

Input Schema

Name	Required	Description
`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.
`listingIds`	Yes	Owner-selected canonical eBay listing IDs from the source operation. Required; duplicates are refused.
`workspaceId`	Yes	The workspace the seller selected. The caller must own it. Required.
`sourceOperationId`	Yes	Source exact pricing operation ID containing retained accepted receipts. 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"
+}

AddedOct 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds valuable context: it returns eligible listing identities, typed conflicts, and missing evidence, and requires manual owner approval in the web app. It could further clarify what 'prepare' persists, but the added details are meaningful.

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?

The description is well-structured and front-loaded: purpose first, then return values, then prerequisites. It is slightly dense but every sentence carries useful information. No wasted words, though the workflow steps could be phrased more crisply.

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?

For a workflow-preparation tool with no output schema, the description explains what is returned (eligible listing identities, typed conflicts, missing evidence) and the required sequence. It does not explain what to do with typed conflicts or missing evidence, but it is sufficiently complete for an agent to invoke correctly.

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 all four parameters are fully documented in the input schema. The description does not add semantic meaning beyond the schema for any parameter; it mentions source receipts and listing IDs but does not elaborate on formats or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb ('Prepare') and resource ('new exact eBay pricing approval from selected accepted source receipts'). It clearly distinguishes from sibling get and execute tools, but does not explicitly differentiate from 'spellbook_ebay_pricing_approval_prepare' (non-restoration), leaving potential confusion.

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?

Provides explicit prerequisites: first read the source with spellbook_ebay_pricing_approval_get, obtain owner approval in the web app, then read approval before spellbook_ebay_pricing_approval_execute. It does not mention when to use this tool versus the non-restoration 'prepare' sibling, but the workflow context is clear.

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?