Skip to main content
Glama

Purchase Three-Way Match

bpj_purchase_three_way_match
Read-onlyIdempotent

Match purchase order, receipt and invoice quantities at the agreed price and identify quantity and unit-price exceptions.

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": "<po>",
      "receipt": "<receipt>",
      "billed": "<billed>",
      "agreed": "<agreed>",
      "invoiced": "<invoiced>"
    },
    "name": "bpj_purchase_three_way_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
poYes
agreedYes
billedYes
receiptYes
invoicedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the computation surfaces quantity and unit-price exceptions, which is real behavioral value. It does not disclose the comparison rule (zero tolerance vs. threshold), what happens with partial receipts, or how exceptions are reported, so it is additive but not rich.

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?

One sentence, front-loaded with the core operation and closed by the output purpose (exception identification). No filler or redundancy. It is efficient, though it is arguably under-specified rather than optimally concise for a five-parameter calculation tool.

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?

There is no output schema, so the description carries the burden of describing the return value — yet 'identify quantity and unit-price exceptions' does not say whether the result is a boolean match flag, a list of exception records, or variances with amounts. For a tool with five required numeric inputs and no documented tolerance semantics, an agent cannot predict the response shape or the comparison rule.

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%, but every parameter carries a descriptive title ('Purchase order quantity', 'Invoiced quantity', 'Agreed unit price'), so the baseline is the title-level documentation rather than nothing. The description adds no clarification of the genuinely confusing pair — 'billed' is an invoiced quantity while 'invoiced' is an invoiced unit price — nor does it explain that invoiced price is compared against agreed price. It therefore fails to compensate for the naming ambiguity where it matters most.

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 and resource set: match PO, receipt and invoice quantities at the agreed price, and flag quantity and unit-price exceptions. That is a recognizable three-way-match operation, distinguishable from neighbors like bpj_purchase_price_variance. It stops short of explicitly differentiating itself from those purchase-domain siblings, so it lands at 4 rather than 5.

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 when-to-use or when-not-to-use guidance, no statement of prerequisites (e.g., that a receipt must already exist), and no named alternative. The agent must infer applicability purely from the phrase 'three-way match' and the parameter names.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.