Skip to main content
Glama

BRAINIAC Accounts Payable

Detect invoice anomalies

accounts-payable_invoice-anomaly-detect

Flag amount mismatches, negative figures, date-order problems, and repeated lines that are present on the invoice. Unusual amounts are not guessed from a normal range. Price $0.05 USDC. POST /api/v1/accounts-payable/invoice-anomaly-detect. 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-anomaly-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
invoiceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 disclose real operational context: the $0.05 USDC price, the POST endpoint, and that unpaid calls return 402 without running. It also scopes the detection behavior by excluding range-based guessing. It omits the response shape and whether the operation mutates or stores anything.

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 detection scope, followed by the behavioral caveat, price, and transport. No filler; each sentence carries distinct information. Sentence order could be slightly tighter, with the caveat grouped next to the detections it qualifies.

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

Completeness2/5

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

For a tool with a complex nested input schema, no output schema, and no annotations, the description is thin: it does not say what the response contains (list of flags? severities?), nor how the file versus structured-invoice inputs are handled. The pricing and 402 details are useful but do not fill those gaps.

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 deeply nested objects, so the description must compensate, and it does not. It never explains that input can be either an uploaded file (PDF/plain/CSV) or a structured invoice object, nor which takes precedence when both are supplied — a distinction an agent cannot infer from the schema alone.

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?

Uses a concrete verb ('Flag') and enumerates the four specific checks performed: amount mismatches, negative figures, date-order problems, and repeated lines. This is far more specific than the title alone, though it never names a sibling (e.g. duplicate-detect, which overlaps on 'repeated lines') to draw the 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?

No explicit when-to-use or when-not-to-use guidance relative to the many sibling validation tools. The one scope statement present — 'Unusual amounts are not guessed from a normal range' — does implicitly tell the agent not to expect statistical anomaly detection, but that is a limitation, 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