Skip to main content
Glama

BRAINIAC Accounts Payable

Validate invoice tax

accounts-payable_invoice-tax-validate

Check a printed or supplied tax amount against a printed or supplied rate and subtotal. No statutory tax rate is applied. Price $0.04 USDC. POST /api/v1/accounts-payable/invoice-tax-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-tax-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, the description carries the full burden and does add real operational context: cost ($0.04 USDC), the HTTP endpoint, and the failure mode that unpaid calls return 402 and do not execute. What it omits is the nature of the result — whether it returns a boolean, a discrepancy amount, or a tolerance — and confirmation that the call is non-mutating.

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 behavior, then the constraint, then cost and transport details. No filler. The raw endpoint string is marginally redundant for an MCP caller but is not harmful.

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 validation endpoint with a large nested input schema, no annotations, and no output schema, the definition should describe what a successful response looks like and what counts as a failure of the check itself. Cost and payment behavior are covered well; the return contract and field expectations are not.

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 partially does by distinguishing "printed" input (the file parameter) from "supplied" input (the invoice object), which is a useful mapping an agent would not otherwise infer. It says nothing about which invoice fields drive the check (tax, taxRate, subtotal) or how lines interact, leaving most of a large nested schema unexplained.

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: check a supplied/printed tax amount against a supplied/printed rate and subtotal. The sentence "No statutory tax rate is applied" usefully separates it from a tax-rate-lookup or tax-calculation tool. It does not name a sibling explicitly, so differentiation is by implication rather than by routing.

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: use it to verify a tax figure that already exists on an invoice rather than to compute statutory tax. There is no guidance on when to prefer it over invoice-total-validate or anomaly-detect, nor any stated prerequisites beyond payment.

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