erp-mcp

get_purchase_order

Read-only

Retrieve a single purchase order by its number to inspect order details, line items, and status. Use it to verify order data before posting invoices or answering vendor questions.

Instructions

Get one purchase order by its number.

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": {
      "number": "<number>"
    },
    "name": "get_purchase_order"
  }
}

Input Schema

Name	Required	Description	Default
`number`	Yes

Output Schema

Name	Required	Description	Default
`amount`	Yes
`number`	Yes
`status`	Yes
`currency`	Yes
`invoiced`	Yes
`remaining`	Yes
`vendor_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

C2.9/5.0

Behavior2/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 no behavioral context beyond that: nothing about not-found behavior, whether the number format is validated, or whether the result is a snapshot versus live data.

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. It is efficient, though the brevity borders on under-specification for a lookup tool.

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?

An output schema exists, so return values need no explanation, and the operation is a simple read. Still, for a keyed lookup the description leaves the agent without guidance on identifier format or failure behavior.

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 0% for the single 'number' parameter, so the description must compensate. It does clarify that the parameter is the purchase order's identifying number, but says nothing about expected format, prefix conventions, or what happens with an unknown number.

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 specific verb (get) and resource (purchase order) with singular scope ('one'), which implicitly separates it from list_purchase_orders. It does not explicitly name the sibling, so differentiation is inferable rather than stated.

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?

The phrase 'by its number' implies the precondition of already knowing the identifier, but there is no explicit when-to-use guidance and no routing to list_purchase_orders or search_vendors when the number is unknown.

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

Deploy Server