Skip to main content
Glama

spellbook_channel_lane_targets

Read-onlyIdempotent

Read the listings SpellBook Finance plans on one channel-lane marketplace for a workspace. It returns the lane's enabled flag, mode, and ask floor, then one target per listing: the card, the copies it holds, the desired quantity and ask, whether the marketplace confirmed both, and what SpellBook last read from the marketplace for it. Pass itemIds to ask about specific scanned copies. Each named copy no target holds comes back in itemsWithoutTarget with a reason. Call it after spellbook_marketplace_onboarding when a seller asks what will list, what is live, or why a card did not list. Call spellbook_channel_lane_set to change the lane's mode or ask floor.

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>",
      "marketplace": "<marketplace>"
    },
    "name": "spellbook_channel_lane_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum targets per page, 1 to 200. Omit for 100. Ignored when itemIds is set.
cursorNoOpaque cursor from a previous page, passed back unchanged. Omit to start from the first page.
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.
itemIdsNoItem ids of copies to look up, 1 to 100. The reply holds every target that contains one of them and a reason for each one no target holds. Omit to page through every target.
marketplaceYesThe channel-lane marketplace whose listing targets to read.
workspaceIdYesThe workspace whose listing targets to read. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial context beyond the read-only, idempotent annotations: it describes the lane-level return fields, the per-target return fields, marketplace confirmation state, last-read state, and the itemsWithoutTarget reason behavior. That is meaningful transparency for a read tool with no output schema.

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?

The purpose is front-loaded, and the description proceeds through return shape, filtering behavior, when to call it, and the mutation alternative. Despite being fairly long, every sentence carries useful information for this complex read tool.

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 six-parameter read tool with no output schema, the description is complete: it explains what is returned, how itemIds changes the result, what itemsWithoutTarget means, and when to use the sibling setter. Remaining details such as pagination are covered by the input schema.

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 the schema already documents all six parameters, including itemIds, pagination, and analytics context. The description mentions itemIds behavior, but mostly reinforces what the schema already says rather than adding new parameter semantics.

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?

The description states a specific verb and resource: it reads listing targets for one channel-lane marketplace in a workspace. It also distinguishes the tool from its sibling spellbook_channel_lane_set by explicitly assigning mode and ask-floor changes to that tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage conditions: call it after spellbook_marketplace_onboarding when a seller asks what will list, what is live, or why a card did not list. It also names the alternative for changes and explains the itemIds lookup path.

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