Skip to main content
Glama

link_po

Links an invoice with no usable PO reference to a specified purchase order, enabling accounts-payable matching and approval workflows.

Instructions

Link an invoice that has no usable PO reference to a purchase order.

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

Input Schema

NameRequiredDescriptionDefault
po_idYes
invoice_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for what is plainly a mutation. It says nothing about reversibility, whether the link can be replaced or unlinked, what happens to an existing PO association, permission requirements, or failure modes; the agent must guess at the consequences of calling it.

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?

A single front-loaded sentence with no filler or redundant restatement of the name. It is efficiently written, though its brevity comes at the cost of the behavioral detail noted elsewhere rather than being an independent strength.

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

Completeness2/5

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

For a two-required-parameter mutation tool with no annotations, no output schema, and zero parameter documentation, this definition is under-specified. An agent has no information about what a successful link returns, whether the operation is idempotent, or how errors (invalid PO, invoice already linked, closed period) manifest.

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 0%, so the description should compensate, and it only partly does: it names both resources, making 'invoice_id' and 'po_id' interpretable from their names. It adds no format, source, or disambiguation guidance (e.g. where po_id comes from or what counts as a valid one), leaving the required-only schema to speak for itself.

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 uses a specific verb ('Link') with two concrete resources ('invoice', 'purchase order') and even states the precondition that the invoice has no usable PO reference. An agent can tell this is the association-creating tool rather than a getter or a payment tool, though it never names a sibling alternative 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?

The clause 'an invoice that has no usable PO reference' gives a usable when-to-use condition, which is more than most definitions offer. However, there is no when-not guidance (e.g. what to do if the invoice already has a PO), no mention of prerequisites such as approval state, and no routing to alternatives.

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