Skip to main content
Glama

rr_get_purchase_order_pdf

Read-onlyIdempotent

Locate where to render a purchase order as a PDF by PO ID or PO number, returning the ReplenishRadar address and PO number—not the PDF file itself.

Instructions

Find where to open a purchase order as a PDF. Returns the PO number and the address in ReplenishRadar that renders the PDF, not the file itself.

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_get_purchase_order_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
po_idYesThe purchase order id or its PO number, for example REV-PO-002.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A3.8/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 fully covered by structured data. The description's added value is stating exactly what comes back (PO number plus the ReplenishRadar address) and that no file is produced, but it says nothing about behavior when the PO is missing or whether the address is authenticated/expiring.

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 with zero filler, and the most decision-relevant fact — that it returns a location rather than the file — is placed up front. Every clause earns its place.

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 no output schema, the description carries the burden of explaining the return shape, and it does so concisely (PO number + rendering address). It is nearly complete for a one-parameter read tool; only error/not-found behavior is 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 coverage is 100% and the single po_id parameter already documents that it accepts an id or a PO number with an example. The description adds no further semantics beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 ('Find where to open a purchase order as a PDF') and immediately disambiguates the result ('the address ... that renders the PDF, not the file itself'). This separates it cleanly from a tool like rr_get_purchase_order that would return the order data, and from any document-listing sibling.

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 return-value clarification: call this when you need a link/URL to view the PDF rather than the PDF bytes or the PO record. However, it never explicitly says when to prefer this over rr_get_purchase_order or rr_list_purchase_order_documents, and gives no prerequisites.

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