Skip to main content
Glama

BRAINIAC Accounts Payable

Extract invoice data

accounts-payable_invoice-data-extract

Extract supplier, invoice number, dates, currency, purchase-order number, terms, and amounts from a supplied invoice or a text-based PDF. Missing fields stay unavailable. No tax rule or payment term is invented. Price $0.06 USDC. POST /api/v1/accounts-payable/invoice-data-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-data-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
invoiceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 disclose useful behavior: missing fields stay unavailable, no tax rule or payment term is invented, the call costs $0.06 USDC, and unpaid calls return 402 without running. It still says nothing about the response payload, latency, or what happens when both inputs are supplied or neither is.

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 short sentences, front-loaded with the what and the input modes, then constraints and cost. The endpoint string and pricing sentence are compact and useful; nothing is filler, though the telegraphic style leaves gaps.

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

Completeness4/5

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

For a no-output-schema extraction tool with two nested optional inputs and no annotations, the definition covers what is extracted, the non-fabrication guarantee, and the payment failure mode. The remaining gap is return-value shape and the requirement that at least one input be provided.

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% and both parameters are deeply nested, so the description must compensate. It partially does by mapping 'a supplied invoice' to the invoice object and 'a text-based PDF' to the file parameter, and by naming the fields that matter, but it omits the media-type/base64 size limits and the precedence between the two inputs.

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 ('Extract supplier, invoice number, dates, currency, purchase-order number, terms, and amounts from a supplied invoice or a text-based PDF') and enumerates the fields produced. It does not explicitly distinguish itself from close siblings like invoice-line-item-extract or payment-terms-extract, even though it claims to return terms too.

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?

Usage is only implied: the two accepted input modes are named, and the phrase 'text-based PDF' implicitly excludes scanned/image PDFs. There is no explicit when-to-use versus the line-item, payment-terms, or validation siblings, and no statement about whether one of the two inputs is required.

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