Skip to main content
Glama

BRAINIAC Accounts Payable

Validate invoice totals

accounts-payable_invoice-total-validate

Recompute the total from line amounts, subtotal, tax, discount, and shipping figures that are actually present. A missing figure is not treated as zero. Price $0.04 USDC. POST /api/v1/accounts-payable/invoice-total-validate. 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-total-validate"
  }
}

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 at all, the description carries the full burden and does well: it discloses the cost ($0.04 USDC), the transport (POST endpoint), and the failure mode (unpaid calls return 402 and do not run). The 'missing figure is not treated as zero' rule is a genuinely useful behavioral disclosure. It does not say what a successful response contains, which is the main remaining gap.

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 core computation, then the missing-figure rule, then pricing and transport. The endpoint URL is arguably redundant but is defensible context; nothing else is padded.

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 two-parameter tool with nested objects, no annotations, and no output schema, the description covers behavior, cost, and error handling but not the shape of the validation result or the role of the file input. An agent can invoke it but cannot predict what it gets back or which input form is expected.

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 must compensate. It does explain which invoice figures participate (line amounts, subtotal, tax, discount, shipping) and how absent figures are handled, but it says nothing about the file parameter (PDF/plain/CSV base64 upload) or how file and invoice inputs relate, and with zero required parameters the agent is left guessing which to supply.

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 names a specific verb and resource: recompute the invoice total from its component figures. It implicitly separates itself from siblings like invoice-tax-validate by focusing on the total arithmetic, 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 Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the arithmetic-check tool, but there is no explicit when-to-use or when-not-to-use guidance relative to tax-validate or anomaly-detect. The pricing and 402 note are prerequisites, not 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