Skip to main content
Glama

get_vendor_purchase_orders

Read-only

READ-ONLY (Vendor). Lists Vendor purchase orders in the last days_back days, with PO number, state and ship-from party. Use get_vendor_purchase_order_details for the lines.

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": "get_vendor_purchase_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
days_backNoQuanti giorni indietro partire da oggi (intero, es. 30).
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
po_item_stateNoStato righe ordine Vendor, es. Accepted, Closed.
include_detailsNotrue = include il dettaglio completo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / days_back / description
      Added value: +"Quanti giorni indietro partire da oggi (intero, es. 30)."
    • addedInput schema / properties / include_details / description
      Added value: +"true = include il dettaglio completo."
    • addedInput schema / properties / po_item_state / description
      Added value: +"Stato righe ordine Vendor, es. Accepted, Closed."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so 'READ-ONLY (Vendor)' restates structured data. The description does add useful content about which fields come back, but says nothing about pagination, result caps, default lookback window, or how include_details interacts with the recommendation to use the details tool.

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 short sentences, with the read-only note and the scope front-loaded before the alternative-tool pointer. No filler and nothing buried.

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 list tool with no required parameters and no output schema, the description covers what it returns and where to get detail. Missing only edge behavior an agent would want: default lookback when days_back is omitted and whether results are capped or paginated.

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%, so the schema already documents all four parameters including the account_id fallback and po_item_state examples. The description only echoes the days_back window and field list, adding no syntax, defaults, or limits beyond the schema.

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?

Specific verb and resource (lists Vendor purchase orders) plus a scope (last days_back days) and an enumerated set of returned fields (PO number, state, ship-from party). It also names the sibling that carries line-level data, so an agent can distinguish the two without opening either schema.

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?

Explicit routing: fetch line items via get_vendor_purchase_order_details, which directly answers the most likely follow-up question. No guidance on when to omit days_back or when include_details should be preferred over the sibling tool, which keeps it below a 5.

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