Skip to main content
Glama

BRAINIAC Accounts Payable

Extract invoice line items

accounts-payable_invoice-line-item-extract

Extract invoice line descriptions, quantities, unit prices, and amounts from supplied lines or selectable document text. Lines that are not present are not created. Price $0.06 USDC. POST /api/v1/accounts-payable/invoice-line-item-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_invoice-line-item-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
invoiceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and delivers real signal: $0.06 USDC cost, POST verb, the endpoint path, and 402 non-execution for unpaid calls. It also guarantees no fabricated lines. It omits auth requirements beyond payment, idempotency, rate limits, and output shape, keeping it short of a 5.

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?

Four dense, front-loaded sentences with no filler; the extraction scope leads and operational facts follow. The raw endpoint path and payment sentences are telegrammatic but each conveys a distinct fact an agent needs.

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 tool with no annotations and no output schema, the definition covers cost, failure mode, and non-fabrication well but leaves the nested input contract and the return shape entirely unexplained. An agent knows what it costs to call but not precisely what to send or what comes back.

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% on a deeply nested schema with file (mediaType/fileBase64/filename) and a large invoice object with up to 200 lines. The description only gestures at 'supplied lines or selectable document text' without mapping that to the file vs. invoice parameters, and gives no format, size, or required-field guidance.

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 (extract) and names the exact fields returned: line descriptions, quantities, unit prices, amounts. It implicitly narrows scope to line items versus sibling tools like invoice-data-extract, though it never names a sibling to sharpen that boundary.

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?

'From supplied lines or selectable document text' hints at two input modes but doesn't say when to choose one over the other, and offers no explicit when-to-use or when-not-to-use versus invoice-data-extract or purchase-order-match. 'Lines that are not present are not created' is a useful behavioral constraint rather than routing guidance.

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