Skip to main content
Glama
ap-agent MCP server

ap-agent MCP server

by Icandi40

list_purchase_orders

Read-only

Retrieve purchase orders filtered by Open or Closed status, or pass an empty string to return all orders for invoice matching and AP review.

Instructions

List purchase orders. status is Open or Closed; pass an empty string for all.

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

Input Schema

NameRequiredDescriptionDefault
statusNoOpen

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 the meaningful default-scope behavior (defaults to Open, empty string returns all), but says nothing about pagination, result limits, or ordering for a list operation that could return many records.

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?

Two short sentences, front-loaded with the purpose and immediately followed by the one parameter rule that matters. Nothing is wasted or repeated from structured fields.

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?

With an output schema present, return values need no explanation, and the single parameter is fully documented. The only gap is operational behavior for a potentially long list (pagination or result caps), which is a minor but real omission.

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

Parameters4/5

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

Schema description coverage is 0% and the status property has no enum, so the description carries the burden and does it well: it names the valid values (Open, Closed) and the non-obvious empty-string sentinel for 'all'. It does not mention case sensitivity or what happens with an invalid value, keeping it from a 5.

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 states a specific verb and resource ('List purchase orders'), which is enough to separate it from the sibling get_purchase_order by the list-vs-single pattern. It does not explicitly name or contrast with that sibling, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by 'List purchase orders' and the default status of Open, but there is no explicit guidance on when to use this versus get_purchase_order or the list_* siblings. The only directional guidance is about the status argument, not tool selection.

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