Skip to main content
Glama

rr_list_purchase_order_notes

Read-onlyIdempotent

Retrieves all notes for a specific purchase order, ordered newest first, so you can review PO history and recent updates.

Instructions

Get all notes for a purchase order, most recent 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_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page (default 1000, max 1000).
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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the sort order ('most recent first'), which is genuine context beyond annotations, but says nothing about pagination behavior, result size, or what a note record contains.

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 sentence with nothing wasted; the ordering guarantee is included at no cost and the content is front-loaded. Appropriate length for a simple read tool.

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 simple three-parameter read operation with full annotation coverage and full schema coverage, the definition gives enough to call it correctly. The remaining gap is the return shape, and since no output schema exists, a brief note on what a note record looks like would have closed the loop.

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%, including the po_id example (REV-PO-002), limit defaults/maximums, and the cursor contract, so the baseline is 3. The description adds no parameter meaning beyond the schema, and notably does not restate that po_id accepts either an internal id or a PO 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?

The description states a specific verb ('Get') and resource ('all notes for a purchase order') and adds an ordering guarantee ('most recent first'). It is clearly distinguishable from write siblings like rr_add_purchase_order_note, though it does not name any sibling explicitly.

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 name and resource scope: fetch the note thread for one purchase order. There is no explicit when-to-use, when-not-to-use, or named alternative guidance, so the agent must infer that this is the read path versus rr_add_purchase_order_note.

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