erp-mcp

list_purchase_orders

Read-only

Retrieve a vendor's purchase orders and see the open amount on each, with status and pagination filters to review outstanding commitments.

Instructions

List a vendor's purchase orders with the amount still open on each.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vendor_id": "<vendor_id>"
    },
    "name": "list_purchase_orders"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`status`	No		open
`vendor_id`	Yes	Vendor id from search_vendors, e.g. V1001

Output Schema

Name	Required	Description
`items`	Yes
`total`	Yes
`next_offset`	Yes	Pass as offset to get the next page; null on the last page

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral detail — each row carries the remaining open amount — but stays silent on the significant default that only status=open records are returned, which materially shapes results.

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; the resource and scope come first. It is efficient, though its brevity is partly the source of the missing behavioral detail rather than a deliberate trade-off.

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 an output schema present and annotations covering safety, the description does not need to explain return values or side effects. However, for a 4-parameter filtered-list tool, omitting the default status filter and pagination behavior leaves an agent able to call it correctly but potentially misunderstanding the result set.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, so the description should compensate, yet it never explains status, limit, or offset. It implies vendor scoping and mentions "open" amounts, but does not clarify that status defaults to "open" or that pagination caps at 50 — the two parameters most likely to cause wrong results.

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 a vendor's purchase orders") plus a scope qualifier (per-vendor) and a hint at payload content ("amount still open on each"). It is clearly distinguishable from get_purchase_order by the singular/plural and list framing, but it never explicitly contrasts with siblings.

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 statement about when to prefer get_purchase_order for a single PO, and no mention of prerequisites such as resolving vendor_id first. Usage is only implied by the phrase "a vendor's purchase orders."

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

Deploy Server