Skip to main content
Glama

BRAINIAC Fraud & Transaction Security

Cluster related fraud accounts

fraud-signals_multi-account-fraud-cluster

Group potentially related accounts using deterministic overlap of caller-supplied emails, phones, devices, IPs, and payment-instrument last4 values. Linkage is not confirmed fraud. Price $0.05 USDC. POST /api/v1/fraud-signals/multi-account-fraud-cluster. 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_multi-account-fraud-cluster"
  }
}

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.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose several non-obvious traits: linkage is deterministic, results are not confirmed fraud, the call costs $0.05 USDC, it is a POST to a specific path, and unpaid calls return 402 without running. It does not say what output is produced, what minimum input is required, or what happens with partial/conflicting identifiers.

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 tight sentences with the core purpose front-loaded, then the caveat, then cost and endpoint/gating details. Little waste, though the endpoint path and the $0.05 line are more operational than semantic.

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?

Given 16 parameters, deep nested schemas, no output schema, and no annotations, the definition covers purpose and payment behavior but leaves input-shape selection (which container to use) and the meaning of the threshold/window knobs entirely unexplained. It is adequate to identify the tool but not fully sufficient to invoke it correctly on first try.

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 and nested objects, and the description only alludes to identifier fields inside identities/payments/transactions. It says nothing about the csv/json/text/file/files containers, asOf, or the eight window/threshold parameters (refundWindowDays, velocityWindowMinutes, velocityCountThreshold, etc.), whose defaults and effects are critical and undocumented.

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 ('Group') and resource ('potentially related accounts') plus the exact linkage method (deterministic overlap of emails, phones, devices, IPs, and payment-instrument last4). That is enough to separate it from siblings like chargeback or velocity analyzers, though it never names an alternative to route against.

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 statement of when to choose this over fraud-signals_chargeback-pattern-analyze or the other signal tools, and no prerequisites or exclusions. The only interpretive hint is 'Linkage is not confirmed fraud', which is about reading results rather than deciding when to call it.

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