Skip to main content
Glama

spellbook_sku_price_controls

Read-onlyIdempotent

Read one seller SKU's exact minimum floor and exact-price lock by printing, finish and condition. Returns saved values, timestamps, all-marketplaces lock scope and whether the seller protected the lock from agent changes. Call it before changing a floor or lock, then read it again after a write.

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>",
      "scryfallId": "<scryfallId>",
      "finish": "<finish>",
      "condition": "<condition>"
    },
    "name": "spellbook_sku_price_controls"
  }
}

Input Schema

NameRequiredDescriptionDefault
finishYesThe exact finish for the SKU: nf, fo, etched, surge, rh, 1e or 1e-fo. Required.
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.
conditionYesThe exact physical condition for the SKU. Required.
scryfallIdYesThe exact Scryfall printing id. Required.
workspaceIdYesThe workspace the seller selected. The caller must own it. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description goes beyond that by disclosing what comes back: saved values, timestamps, all-marketplaces lock scope, and whether the seller protected the lock from agent changes — valuable since there is no output schema. Missing only edge behavior (e.g. what is returned when no floor or lock is set).

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?

Two sentences, both front-loaded and content-bearing: the first establishes what is read and what is returned, the second establishes the workflow. No repetition of the name or filler.

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 read-only, four-required-parameter tool with no output schema, the description covers the identifying key, the returned data shape, and the read-before/read-after write workflow. An agent has everything needed to call it correctly and interpret the result.

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?

With 100% schema description coverage, the schema already documents every parameter including the two enums. The description adds the useful signal that printing, finish and condition together form the SKU's composite key, but nothing about workspaceId ownership requirements or the optional context field. Baseline 3 is appropriate when the schema carries the detail.

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 (read) and a precisely scoped resource (one seller SKU's minimum floor and exact-price lock), plus the identifying dimensions: printing, finish, condition. An agent can distinguish it at a glance from the write siblings like spellbook_sku_minimum_floor_set or spellbook_sku_exact_price_lock_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?

Gives explicit lifecycle guidance: 'Call it before changing a floor or lock, then read it again after a write,' which effectively positions it as the read companion to the set/clear tools. It stops short of naming those sibling tools or stating when not to use this one, so it is clear context rather than full routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources