Skip to main content
Glama

BRAINIAC Accounts Payable

Extract payment terms

accounts-payable_payment-terms-extract

Read payment terms only when they are supplied or printed, including Net N, due on receipt, and a stated discount such as 2/10 Net 30. Price $0.03 USDC. POST /api/v1/accounts-payable/payment-terms-extract. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "accounts-payable_payment-terms-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
invoiceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the cost ($0.03 USDC), the transport (POST /api/v1/...), and the failure mode for unpaid calls (402, does not run). It omits what happens when no terms are found in the document, which matters for an extraction tool.

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?

Three compact sentences, purpose front-loaded, then pricing and endpoint, then the payment failure mode. No filler, though the endpoint string and price sit slightly awkwardly mid-description.

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 paid, payment-gated extraction endpoint with nested inputs and no output schema, the description covers cost and failure but not the return shape (extracted term fields, null/empty behavior) or the role of the invoice object. Adequate to call correctly, not adequate to interpret results.

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?

Schema description coverage is 0% across two nested-object parameters, and the description never mentions 'file' or 'invoice'. An agent gets no guidance on accepted media types, size limits, or why an invoice payload should accompany the file — the schema alone must be reverse-engineered.

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?

States a specific verb and resource ('Read payment terms') and scopes it to terms that are 'supplied or printed', naming concrete forms (Net N, due on receipt, 2/10 Net 30). This implicitly separates it from the calculation sibling, though it never names an 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 Guidelines4/5

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

Gives a clear gating condition: use only when terms are supplied or printed, i.e. do not infer them. It stops short of naming the alternative (e.g. payment-due-date-calculate) for the inference case, so the routing is implied rather than spelled out.

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.

Resources