Skip to main content
Glama

BRAINIAC Accounts Payable

Detect duplicate invoices

accounts-payable_invoice-duplicate-detect

Compare one invoice with other invoices supplied in the same request using the supplier and invoice number, and a content fingerprint. This does not search an accounts payable ledger. Price $0.05 USDC. POST /api/v1/accounts-payable/invoice-duplicate-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-duplicate-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
invoiceNo
candidatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the matching keys, the comparison basis, the price ($0.05 USDC), the transport, and the failure mode (unpaid calls return 402 and do not run). It does not describe the shape of the comparison result, which matters most for a no-output-schema tool.

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?

Front-loaded with purpose, then scope exclusion, then operational facts. Every sentence carries information, though the price/endpoint/402 trio is boilerplate that could be compressed into one clause without losing meaning.

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 nested-object tool with no annotations and no output schema, the description covers intent and pricing well but leaves two gaps: the file-vs-structured-invoice input relationship and any indication of what the duplicate comparison returns (match flags, confidence, matched candidate ids). An agent can call it, but must guess at both input selection and result interpretation.

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% across three top-level parameters, so the description must compensate. It hints that 'invoice' is the subject and 'candidates' the comparison set via 'other invoices supplied in the same request' and names the matching fields, but it never explains the relationship between the optional 'file' upload and the structured 'invoice' object, nor which inputs are actually required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and scope: 'Compare one invoice with other invoices supplied in the same request using the supplier and invoice number, and a content fingerprint.' The explicit negative scope — 'This does not search an accounts payable ledger' — is exactly the kind of disambiguation that separates this from ledger-style or extraction siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear when-to-use context (you already hold the candidate invoices and want pairwise comparison) and an explicit when-not (no ledger lookup). It stops short of naming alternatives such as purchase-order-match or anomaly-detect for related checks, so the agent must infer routing from the negative scope alone.

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