Skip to main content
Glama

get_vendor_po_summary

Read-only

Vendor PO aggregate summary

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / days_back / description
      Added value: +"Quanti giorni indietro partire da oggi (intero, es. 30)."
  2. First observed

TDQS

C2.2/5.0
Behavior2/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 the safety profile is covered structurally. The description adds nothing beyond that — no information on what the aggregation covers, its default time window, or the shape/size of the result, which matters for a summary tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is only a four-word noun phrase, so it is short but under-specified rather than concise. There is nothing front-loaded because there is no content to order.

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

Completeness2/5

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

For a read-only aggregate tool with two optional, fully documented parameters and no output schema, the description should at minimum say what the summary contains and over what default period. Neither is present, leaving the agent to guess the return semantics of the aggregate.

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 both parameters (days_back, account_id) are documented in the schema, so the baseline is 3. The description contributes no additional meaning about how days_back interacts with the aggregation or what account_id scoping does to the totals.

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

Purpose2/5

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

"Vendor PO aggregate summary" essentially restates the tool name and title without adding a verb or specifying what is aggregated (counts, spend, open/closed POs, per-vendor totals). It does not differentiate this tool from siblings like get_vendor_purchase_orders or get_vendor_purchase_order_details, so an agent cannot tell which one to pick from the description alone.

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 guidance, no mention of when to prefer it over the detailed PO siblings, and no stated preconditions. The only usage hint comes from the schema (account_id optional when the token is bound to a single outpost), which is not part of the description.

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