Skip to main content
Glama

BRAINIAC Fraud & Transaction Security

Assess supplier bank-change risk

fraud-signals_supplier-bank-change-risk

Identify suspicious supplier bank-detail changes near invoice timing from caller-supplied records. Bank values are last4-masked. Price $0.04 USDC. POST /api/v1/fraud-signals/supplier-bank-change-risk. 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_supplier-bank-change-risk"
  }
}

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, the description still discloses meaningful behavior: it operates only on caller-supplied records (no external enrichment), bank values must already be last4-masked, it costs $0.04 USDC, and unpaid calls return 402 without executing. It says nothing about what the analysis returns, whether results are scored/ranked, or how partial or malformed inputs are handled.

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 purpose, followed by data-handling, pricing, and transport facts; nothing is padded. The endpoint path is mildly redundant with the tool name but still operationally useful.

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 parameters, nested objects, no output schema, and no annotations, the description is thin: it never explains the input record model or what a caller receives back beyond a 402 failure. A caller cannot construct a correct payload from this description alone.

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, including nested invoice/payment/identity/transaction arrays and several threshold knobs (bankChangeRiskHours, velocityWindowMinutes, velocityCountThreshold). The description adds only the last4-masking convention for bank values and explains none of the record groups, threshold semantics, or how csv/json/text/files inputs relate to the structured arrays.

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+resource (identify suspicious supplier bank-detail changes) and narrows scope to changes near invoice timing, which implicitly separates it from siblings like invoice-fraud-signal-detect or payment-fraud-pattern-detect. It does not explicitly name an alternative, so it stops just short of a 5.

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?

The phrase 'near invoice timing' and 'from caller-supplied records' implies the scenario in which this tool applies, and the 402 note implies a payment prerequisite. There is no explicit when-to-use vs. when-not-to-use guidance or named alternative among the seven siblings.

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