SpellBook Finance

spellbook_deck_import_limitless

Idempotent

Import one player's Pokemon decklist from one fixed Limitless tournament standings record into the seller's workspace. The workspace owner chooses the event, player, format and idempotency key; retries with the same key replay the first result or report an in-progress import. The tool does not accept URLs or credentials and returns source identity, matched and unmatched counts, and the imported deck.

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>",
      "eventId": "<eventId>",
      "playerId": "<playerId>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "spellbook_deck_import_limitless"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Optional deck name.
`format`	No	Deck format. Defaults to Standard.	Standard
`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.
`eventId`	Yes	The Limitless tournament event id. Required.
`playerId`	Yes	The exact player name or id as shown by the selected event. Required.
`workspaceId`	Yes	The workspace to import into. The caller must be its owner. Required.
`idempotencyKey`	Yes	A caller-generated retry key. Reuse it unchanged after an uncertain result. 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"
+}

AddedSep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds real context beyond the annotations: idempotency replay semantics ('retries with the same key replay the first result or report an in-progress import'), the no-URL/credentials constraint, and the return contents (source identity, matched/unmatched counts, imported deck) which matters given there is no output schema. It stops short of covering permission requirements or failure modes explicitly, so a 4.

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 sentences, zero filler, with the core action front-loaded and the retry rules and return shape following in logical order.

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 7-parameter mutation with no output schema, the description covers the source, the caller's ownership, idempotency behavior, excluded inputs, and the return payload — everything an agent needs to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds value by framing who supplies the event/player/format/idempotency key and by characterizing the retry contract of idempotencyKey. That elevates it slightly above the schema-only baseline.

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 (import) and a tightly scoped resource (one player's decklist from one fixed Limitless tournament standings record) into the seller's workspace. This is clearly distinguishable from siblings like spellbook_deck_contents (read) or spellbook_inventory_import_csv (bulk inventory).

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?

Explains the operating context ('one fixed Limitless tournament standings record', 'seller's workspace') and explicitly rules out URL/credential inputs. It does not name a specific alternative sibling for related tasks, which keeps it from a 5, but the when/when-not framing 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?