Skip to main content
Glama

BRAINIAC Fraud & Transaction Security

Analyze transaction velocity

fraud-signals_transaction-velocity-analyze

Identify abnormal transaction frequency and amount velocity from caller-supplied histories. Velocity spikes alone are never labeled confirmed fraud. Price $0.04 USDC. POST /api/v1/fraud-signals/transaction-velocity-analyze. 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_transaction-velocity-analyze"
  }
}

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

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavioral facts: a hard cost of $0.04 USDC, the POST route /api/v1/fraud-signals/transaction-velocity-analyze, and that unpaid calls return 402 and do not execute. The statement that velocity spikes alone are never labeled confirmed fraud usefully sets output expectations, but nothing is said about the response shape, rate limits, or what happens with empty/insufficient histories.

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, purpose front-loaded, then the fraud-labeling caveat, then the commercial and transport details. Every sentence carries information; the endpoint path is the least valuable but is short.

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, deeply nested payload schemas, no annotations, and no output schema, the description is thin: it never explains the input envelope (csv/json/text/file/files vs. structured arrays), the tuning thresholds, or what the analysis returns. An agent could not call this correctly without opening the schema and guessing at field semantics.

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/transaction/identity record shapes and the key tuning knobs velocityWindowMinutes, velocityCountThreshold, and velocityAmountThreshold. The phrase 'caller-supplied histories' hints that data goes in via the array inputs, but no parameter is explained — no units, defaults, time format for asOf, or relationship between the count/amount thresholds and the window.

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 ('Identify abnormal transaction frequency and amount velocity from caller-supplied histories'), which clearly separates it from siblings like chargeback-pattern, refund-abuse, or supplier-bank-change analysis. It does not explicitly name an alternative, but the velocity framing is distinctive enough for an agent to route correctly.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over the seven sibling fraud analyzers, nor on prerequisites such as minimum history length or whether at least one data array must be supplied. The only usage-adjacent statement is the caveat that velocity spikes alone are never confirmed fraud, which is interpretation guidance rather than selection 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