Skip to main content
Glama

rr_request_purchase_order_approval

Destructive

Request manager approval for a draft or review purchase order before sending it; approval happens in ReplenishRadar after sign-in, and unapproved sends fail.

Instructions

Ask a manager to approve a draft/review PO. The request expires in 15 minutes and is approved in ReplenishRadar after signing in, not by a link. Use BEFORE rr_send_purchase_order - sending without approval will fail. Supersedes any prior pending request.

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

Input Schema

NameRequiredDescriptionDefault
po_idYesThe purchase order id or its PO number, for example REV-PO-002 (required).
messageNoOptional context for the approver.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare destructive=true, non-idempotent, non-open-world; the description adds substantive behavior: a 15-minute expiry window, that approval happens in-app after signing in rather than via a link, and that any prior pending request is invalidated — which explains the destructive hint. This is exactly the kind of context annotations cannot carry.

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?

Three short sentences, front-loaded with the action, then the expiration/auth constraint, then the ordering dependency. No filler, and each sentence changes how an agent would call the 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?

With no output schema, the description covers the critical flow (request sent, 15-minute expiry, approval happens out-of-band) but never says what the tool returns — e.g. a request id or status — which would help an agent confirm success or poll state. Otherwise complete for a two-parameter mutation.

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%, so both po_id and message are already documented in the schema, including an example format for the PO number. The description adds no further meaning about the parameters, 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: 'Ask a manager to approve a draft/review PO.' It also scopes the action to draft/review-state POs, which distinguishes it from send, cancel, and update siblings without the agent needing to open any schema.

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

Usage Guidelines5/5

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

It gives an explicit ordering rule — 'Use BEFORE rr_send_purchase_order' — plus the consequence of skipping it ('sending without approval will fail'), and it names the alternative path it supersedes ('Supersedes any prior pending request'). When-to-use, when-not-to-skip, and relationship to the sibling are all stated.

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