Skip to main content
Glama
Sign In

SpellBook Finance

by com.spellbook-finance
OverviewDiscussionsAdmin

spellbook_ebay_automation_set

DestructiveIdempotent

Set one workspace's eBay automation mode, basic-land preference, copy cap, or month-end allowance policy after the owner chooses the setting. Month-end defaults to off with a 1,000-insertion reserve. Optional stale-single refreshes run in the final 48 hours and stop new ends two hours before the Pacific month resets. Read spellbook_ebay_month_end_status first for capacity and recovery facts. Only the workspace owner may change public listing behavior. The modes: manual: New listings and repricing stay manual. Recovery of listings already ended by month-end management can finish. auto_list: New eligible inventory lists on eBay automatically at your saved eBay pricing strategy's prices, and existing eBay listings are never repriced automatically. full: New inventory lists on eBay automatically, and existing eBay listings reprice from your saved eBay pricing strategy. With variation packages on (the default), new inventory groups into one listing per set with each card as a variation; with them off, each card lists on its own.

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

Input Schema

NameRequiredDescriptionDefault
modeNoThe mode the seller chose: manual, auto_list, or full. Send mode, basicLandsEnabled, maxQuantityPerListing, or any mix.
contextNoOptional 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.
monthEndNoThe owner's month-end choice: enabled, reserve, and refreshStale. Enabling retains the reserve during automatic listing. refreshStale permits eligible older singles to refresh after new-stock work. Disabling stops new ends; recovery of already-ended stock continues.
workspaceIdYesThe workspace whose eBay automation mode to set. The caller must own it. Required.
basicLandsEnabledNotrue lets auto_list and full list basic lands (Plains, Island, Swamp, Mountain, Forest, Wastes, and their Snow-Covered printings). false skips them. The saved value defaults to false.
maxQuantityPerListingNoThe most available copies one eBay listing may advertise, such as 3. null removes the cap. Omit it to keep the saved value, which defaults to null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / monthEnd
      Added value: +{
+  "additionalProperties": false,
+  "description": "The owner's month-end choice: enabled, reserve, and refreshStale. Enabling retains the reserve during automatic listing. refreshStale permits eligible older singles to refresh after new-stock work. Disabling stops new ends; recovery of already-ended stock continues.",
+  "properties": {
+    "enabled": {
+      "default": false,
+      "type": "boolean"
+    },
+    "refreshStale": {
+      "default": false,
+      "type": "boolean"
+    },
+    "reserve": {
+      "default": 1000,
+      "maximum": 200000,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / maxQuantityPerListing
      Added value: +{
+  "anyOf": [
+    {
+      "exclusiveMinimum": 0,
+      "maximum": 10000,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The most available copies one eBay listing may advertise, such as 3. null removes the cap. Omit it to keep the saved value, which defaults to null."
+}
    • changedInput schema / properties / mode / description
      Previous value: -"The mode the seller chose: manual, auto_list, or full. Send mode, basicLandsEnabled, or both."New value: +"The mode the seller chose: manual, auto_list, or full. Send mode, basicLandsEnabled, maxQuantityPerListing, or any mix."
  4. Changed3 schema fields changed
    • addedInput schema / properties / basicLandsEnabled
      Added value: +{
+  "description": "true lets auto_list and full list basic lands (Plains, Island, Swamp, Mountain, Forest, Wastes, and their Snow-Covered printings). false skips them. The saved value defaults to false.",
+  "type": "boolean"
+}
    • changedInput schema / properties / mode / description
      Previous value: -"The mode the seller chose: manual, auto_list, or full. Required."New value: +"The mode the seller chose: manual, auto_list, or full. Send mode, basicLandsEnabled, or both."
    • changedInput schema / required
      Previous value: -[
-  "workspaceId",
-  "mode"
-]New value: +[
+  "workspaceId"
+]
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag this as a destructive, open-world, idempotent mutation, so the description needn't restate safety. It adds real context beyond that: owner-only authorization, month-end defaulting to off with a 1,000-insertion reserve, refreshes running only in the final 48 hours and stopping new ends two hours before the Pacific month reset, and what each mode does to existing listings. It does not state reversibility of a mode change on already-listed inventory, so a 4 rather than 5.

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 action and the settable fields, then layered with prerequisites, timing, and mode semantics in a logical order. It is long, and the variation-package sentence is somewhat dense, but nearly every sentence carries operational information 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?

For a destructive, owner-gated mutation with a nested monthEnd object and no output schema, the definition covers defaults, timing windows, authorization, and per-mode consequences. It leaves the caller without guidance on what the tool returns or how a change interacts with listings already mid-cycle, which is the remaining gap.

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 the schema already documents parameters and the baseline is 3. The description does go beyond the bare enum by explaining what manual, auto_list, and full actually do, plus the variation-package behavior, but it omits specifics on maxQuantityPerListing and the basic-lands flag that the schema already covers.

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 (set) plus the resource (one workspace's eBay automation mode) and enumerates exactly which settings are covered: mode, basic-land preference, copy cap, month-end allowance policy. This separates it cleanly from the read-only sibling spellbook_ebay_month_end_status and from adjacent setters like spellbook_manapool_automation_set.

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 a clear prerequisite ordering (read spellbook_ebay_month_end_status first for capacity and recovery facts) and an authority constraint (only the workspace owner may change public listing behavior). It does not spell out explicit when-not conditions or failure behavior for non-owner callers, which keeps it short of 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 toolsInspect
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