SpellBook Finance

spellbook_sealed_price_target_create

Create a local sealed retailer price target and return its saved status and observed match facts. Call with an exact product and explicit native-currency threshold. Read spellbook_sealed_price_target next; a target records observations without reserving or purchasing products.

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": {
      "productId": "<productId>",
      "retailerMarketRegion": "<retailerMarketRegion>",
      "currency": "<currency>",
      "destinationCountry": "<destinationCountry>",
      "targetAmount": "<targetAmount>"
    },
    "name": "spellbook_sealed_price_target_create"
  }
}

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.
`currency`	Yes	Native offer currency; no conversion or delivered total is inferred.
`productId`	Yes	Exact catalog productId from sealed product discovery; variants and package sizes are distinct.
`targetAmount`	Yes	Maximum native amount for one exact product unit before shipping and tax.
`destinationCountry`	Yes	Destination ISO country code; shipping eligibility can remain unknown.
`retailerMarketRegion`	Yes	Retailer market to observe; this does not establish delivery eligibility.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

changedInput schema / properties / currency / enum

Previous value: -[
-  "USD",
-  "CAD",
-  "NZD"
-]New value: +[
+  "USD",
+  "CAD",
+  "NZD",
+  "GBP",
+  "EUR"
+]

AddedOct 30, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the write-but-not-destructive profile and open-world scope; the description adds real value on top by clarifying that a target only records observations and never reserves or purchases, and that the target is stored locally. It omits duplicate/non-idempotent behavior, which the annotations flag but the prose never explains.

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?

Three short sentences lead with the action, then the call requirements, then the follow-up and the key semantic caveat. No filler and nothing front-loaded incorrectly.

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 six-parameter mutation with annotations and no output schema, the description covers creation, inputs, non-purchase semantics, and the return shape. Gaps are minor: no mention of entitlement/permission requirements or what happens on a duplicate target.

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 coverage is 100%, so every parameter is already documented, including enums and the native-amount semantics. The description restates 'exact product' and 'explicit native-currency threshold' but adds no syntax or edge-case 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Create a local sealed retailer price target') and states what comes back ('saved status and observed match facts'). It does not distinguish this create from the sibling update/disable/rearm targets, so an agent must infer that this is the initial-creation path.

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?

It gives prerequisites ('exact product and explicit native-currency threshold') and a clear next step ('Read spellbook_sealed_price_target next'). It stops short of naming when to prefer this over spellbook_sealed_price_target_update or _rearm.

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?