Skip to main content
Glama

rr_list_recommendations

Read-onlyIdempotent

Lists pending buying and transfer recommendations, including supplier purchase orders, location transfers, or both, so sellers can review and act on prepared inventory work.

Instructions

List recommendations: the buying and transfer work ReplenishRadar has prepared that is still waiting, as supplier orders, transfers between locations, or both.

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

Input Schema

NameRequiredDescriptionDefault
skuNoOptional SKU filter
kindNoOptional kind filter: supplier_po, transfer, combined, no_action
limitNoActions per page (default 100, max 500).
cursorNonext_cursor from the previous page. Pass it with the same other inputs until has_more is false.
statusNoOptional status filter, comma-separated
store_idNoOptional store ID filter
origin_location_idNoOptional child origin location filter
source_location_idNoOptional parent source location filter
destination_location_idNoOptional parent or child destination location filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description's contribution beyond that is the scope statement that results are pending work only, which is real but modest. It says nothing about pagination behavior, ordering, or result volume despite nine filtering/paging parameters.

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?

A single front-loaded sentence that names the action first and then qualifies scope, with no filler or redundant restatement of the title. The clause "the buying and transfer work ReplenishRadar has prepared that is still waiting" is slightly convoluted but earns its place by defining the domain object.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries some burden for explaining what a recommendation record looks like, and it only gestures at this via the supplier-order/transfer/both taxonomy. With nine optional filters and cursor pagination, an agent can still call it correctly from the schema alone, but ordering, default status scope, and result shape remain unexplained.

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%, and every parameter carries its own inline description including defaults, max/min on limit, and cursor usage. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies. It does not, for example, explain how the kind values relate to the tool's stated supplier-PO/transfer/both framing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("List recommendations") and goes further by defining what a recommendation actually is: pending buying/transfer work expressed as supplier POs, inter-location transfers, or both. That content definition makes the tool distinguishable from generic list siblings at a glance. It stops short of naming a concrete alternative such as rr_list_suggested_purchase_orders or rr_list_transfer_decisions, which keeps it from a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: "still waiting" signals this returns open/pending items, implicitly contrasting with the close/dismiss siblings, and the supplier-PO vs transfer framing hints at when to reach for it. There is no explicit when-to-use or when-not-to-use clause, and no named alternative for the overlapping suggested-PO and transfer-decision listing tools, so the agent must infer routing.

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