Skip to main content
Glama

BRAINIAC Fraud & Transaction Security

Detect synthetic-identity signals

fraud-signals_synthetic-identity-signal-detect

Identify inconsistencies in caller-supplied identity records (sparse profiles, age/postal mismatches, shared contacts). Personal data is masked in responses. Price $0.04 USDC. POST /api/v1/fraud-signals/synthetic-identity-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_synthetic-identity-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

C2.7/5.0
Behavior2/5

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

With zero annotations the description must carry the full behavioral burden. It does disclose genuinely useful traits — PII is masked in responses, cost is $0.04 USDC, unpaid calls return 402 and do not execute — which is more than most definitions offer. However, it says nothing about what a caller gets back (risk score? flags? per-identity verdicts), how partial input is handled, or whether records are stored/retained, all of which matter for a fraud tool ingesting PII.

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, purpose front-loaded, with the detected signal types enumerated early. The pricing and endpoint sentences are terse but each carries operational value; nothing is padded.

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 16-parameter tool with deeply nested objects, multiple alternative input channels, and no output schema or annotations, this description is materially incomplete. An agent could not tell which of the mutually exclusive input shapes to supply or what the numeric threshold parameters do, so successful invocation would require guesswork.

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?

Sixteen parameters with 0% schema description coverage and the description documents none of them. The mention of 'age/postal mismatches' and 'shared contacts' hints at which identity fields (dateOfBirth, postalCode, email/phone) are used, but the existence and purpose of csv/json/text/file/files payload modes, asOf, and the six tunable window/threshold parameters are entirely unexplained.

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 ('Identify inconsistencies') and a specific resource ('caller-supplied identity records'), then lists the concrete signal types it detects (sparse profiles, age/postal mismatches, shared contacts). This clearly separates it from invoice/payment/refund siblings by subject matter, though it never names an alternative tool explicitly.

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 reach for this tool versus the other fraud-signal tools (invoice, payment, refund, chargeback, velocity), nor any preconditions on data volume or quality. The only routing-ish information is the payment/402 note, which governs billing rather than tool selection.

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