Skip to main content
Glama

BRAINIAC Fraud & Transaction Security

Detect invoice fraud signals

fraud-signals_invoice-fraud-signal-detect

Detect potentially manipulated invoices from caller-supplied invoice exports (duplicate numbers, tax anomalies, missing PO). Not confirmed fraud. Price $0.04 USDC. POST /api/v1/fraud-signals/invoice-fraud-signal-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": "fraud-signals_invoice-fraud-signal-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
invoicesNo
paymentsNo
identitiesNo
transactionsNo
refundWindowDaysNo
bankChangeRiskHoursNo
chargebackWindowDaysNo
velocityWindowMinutesNo
velocityCountThresholdNo
velocityAmountThresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations at all, the description does carry real behavioral weight: it discloses the price ($0.04 USDC), the transport (POST endpoint), and that unpaid calls return 402 without running, which is valuable failure-mode context. However, it says nothing about authentication, what the response contains, whether results are persisted, or how the many optional tuning inputs affect behavior, leaving substantial gaps for a zero-annotation mutation-like endpoint.

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 with the purpose front-loaded and no filler; each clause adds either scope, cost, or failure behavior. The raw endpoint string is marginally technical overhead, but it is compact and potentially useful, so the text stays tight overall.

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 16 mostly nested, zero-documented parameters, no output schema, and no annotations, the description is far too thin to let an agent call it correctly. It never clarifies which of the 16 inputs are needed in practice (none are marked required), what the response shape is, or what the detection thresholds do. Billing and 402 behavior are covered, but the bulk of invocation-relevant context is missing.

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 16 parameters, many of them nested objects with dozens of unlabeled fields, so the description is the only source of meaning and it provides almost none. It hints that invoice exports are the input ('csv', 'invoices', 'file' are never mentioned by name) but never explains asOf, refundWindowDays, bankChangeRiskHours, or the velocity thresholds. This is a serious shortfall given the parameter surface.

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 ('Detect potentially manipulated invoices') and enumerates the signals examined: duplicate numbers, tax anomalies, missing PO. It also scopes the output with 'Not confirmed fraud,' which separates it from a confirmed-fraud verdict. It never names a sibling tool explicitly, so differentiation from supplier-bank-change-risk or payment-fraud-pattern-detect is only implied by the invoice focus.

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?

'From caller-supplied invoice exports' tells the agent it must bring its own data rather than query a stored system, which is useful invocation context. There is no explicit when-to-use versus when-to-use-an-alternative guidance and no statement of prerequisites or input minimums, so the agent must infer selection from the sibling names 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