Skip to main content
Glama

rr_list_suggested_purchase_orders

Read-onlyIdempotent

List AI-suggested purchase orders based on stockout risk, demand, and supplier reliability to prioritize replenishment decisions.

Instructions

Get AI-suggested purchase orders based on stockout risk, demand, and supplier reliability.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page (default 100, max 500).
cursorNonext_cursor from the previous page. Pass it with the same other inputs until has_more is false.
statusNoFilter: suggested, approved
store_idNoOnly suggestions for this store.
vendor_idNoFilter by vendor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

B3.2/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. The description adds useful context about what drives the suggestions, but says nothing about what a suggestion record contains or whether suggestions can be acted on directly.

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 with no filler, which is appropriate for a simple list tool. It is efficient but leaves the definition under-specified rather than over-worded.

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?

With five optional parameters, no output schema, and full annotation coverage, the definition is minimally adequate to call the tool. It omits how suggestions differ from real purchase orders and how they relate to sibling recommendation tools, which is the main gap an agent would face.

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%, with limit, cursor, status, store_id, and vendor_id all documented inline including pagination semantics. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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?

States a concrete verb and resource ('Get AI-suggested purchase orders') plus the ranking basis (stockout risk, demand, supplier reliability), which makes the 'suggested' qualifier meaningful. It does not explicitly distinguish itself from the sibling rr_list_purchase_orders, so an agent must infer that this returns AI-generated suggestions rather than real POs.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative, despite siblings like rr_list_purchase_orders, rr_list_recommendations, and rr_list_stockout_risks that overlap conceptually. The agent must guess which listing tool to call.

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