Skip to main content
Glama

rr_list_transfer_decisions

Read-onlyIdempotent

Show why products were or were not transferred between your own locations on the last run, for one SKU or the whole population with reason counts.

Instructions

Why products were, or were not, moved between the seller's own locations on the last transfer run. Pass a sku for one product's answer; omit it for the whole population with counts by reason. It answers why something was not transferred or restocked from another location, which an empty transfer-suggestions list does not say.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rr_list_transfer_decisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuNoOne product's answer. Omit for the population. There is deliberately no store filter: the transfer census is org-grain, because transfer generation resolves its locations org-wide.
limitNoRows per page (default 2000, max 2000).
cursorNonext_cursor from the previous page. Pass it with the same other inputs until has_more is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world status. The description adds behavior beyond them: the census is org-grain by design (no store filter), and results are paged via cursor. It stops short of describing what each row contains, but the safety and scope profile is well covered.

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, front-loaded with purpose, then parameter routing, then the disambiguating contrast with transfer suggestions. No filler; every clause carries information.

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 read-only three-parameter list tool with no output schema, the definition covers purpose, scoping and pagination adequately. It does not sketch the returned row shape (fields besides the reason counts), which is the remaining gap given the absence of an output 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 description coverage is 100%: the sku, limit and cursor semantics, including the org-grain rationale for the absent store filter, are already in the schema. The description restates the sku-vs-population split and adds 'counts by reason', but little meaning beyond the structured fields.

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 and resource: explaining why products were or were not moved between the seller's own locations on the last transfer run. It also explicitly differentiates itself from an empty transfer-suggestions list, so the agent can tell it apart from sibling list tools without opening a schema.

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?

Gives concrete use conditions: pass a sku for a single product, omit it for the population with counts by reason. It also names the situation that selects this tool over transfer suggestions — when something was not transferred or restocked and the suggestions list is empty.

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