Skip to main content
Glama

rr_list_purchase_order_documents

Read-onlyIdempotent

List documents attached to a purchase order, newest first, with cursor-based pagination to review supporting files page by page.

Instructions

List the documents attached to a purchase order, newest first.

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": {
      "po_id": "<po_id>"
    },
    "name": "rr_list_purchase_order_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page (default 100, max 500).
po_idYesThe purchase order id or its PO number, for example REV-PO-002
cursorNonext_cursor from the previous page. Pass it with the same other inputs until has_more is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and a closed world, so the safety profile is covered structurally. The description's only addition is the "newest first" ordering, which is genuinely useful, but it says nothing about empty results, what a "document" is, or whether documents can be downloaded from the response.

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?

A single front-loaded sentence with zero padding; the ordering constraint is placed where it is most visible. Nothing could be removed without losing information.

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, three-parameter paged list with full schema coverage and explicit annotations, the description covers the essentials. Without an output schema, however, it leaves the shape of returned documents and the meaning of has_more/next_cursor unstated.

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%: po_id accepts a PO number like REV-PO-002, and limit/cursor are documented with paging semantics. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 and resource ("List the documents attached to a purchase order") plus a scope detail ("newest first"). That cleanly separates it from the note-listing and PDF-getting siblings, though it never names an alternative to route against.

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 the narrow resource: fetch attachment metadata for one PO. There is no explicit when-to-use or when-not-to-use guidance, and nothing tells the agent how this differs from getting the PO itself or its PDF.

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