Skip to main content
Glama

get_po

Retrieves a purchase order's ordered and received quantities plus goods receipts by PO ID, helping accounts-payable agents verify invoice details before approval or payment.

Instructions

A purchase order with ordered and received quantities and goods receipts.

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

Input Schema

NameRequiredDescriptionDefault
po_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses returned content (ordered/received quantities and goods receipts), but does not state that it is read-only, what happens if the PO is missing, or any permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no wasted wording and the useful return-content details are front-loaded. The fragment style is slightly informal but still efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter getter with no output schema, the description gives helpful return-value context. However, it omits parameter meaning and behavioral details that the absent annotations do not cover.

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

Parameters2/5

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

The schema has 0% description coverage for the sole required parameter, po_id, and the description does not explain its format, source, or expected value. With low schema coverage the description should compensate, but it does not.

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 names the resource and states what it contains: a purchase order with ordered and received quantities and goods receipts. The tool name supplies the retrieval verb, so purpose is clear, though the description does not explicitly distinguish get_po from list_pos or link_po.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus siblings such as list_pos, link_po, or get_invoice. The description does not mention prerequisites, error cases, or selection criteria.

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