Skip to main content
Glama

BRAINIAC Fraud & Transaction Security

Detect payment fraud patterns

fraud-signals_payment-fraud-pattern-detect

Detect suspicious combinations of caller-supplied payment events (declines-then-success, instrument churn, billing/shipping mismatch). Anomalies are not confirmed fraud. Price $0.05 USDC. POST /api/v1/fraud-signals/payment-fraud-pattern-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_payment-fraud-pattern-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.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden, and it discloses meaningful operational traits: a $0.05 USDC price, the POST endpoint, and that unpaid calls return 402 and do not execute. It also sets expectations that results are anomalies, not confirmed fraud. It omits auth requirements, rate limits, and return shape, keeping it from a 5.

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 and pattern types followed by disclaimers and billing terms; nearly every sentence earns its place. The endpoint path partially duplicates the tool identity but is defensible for an HTTP-backed paid tool.

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 nested objects, multiple mutually substitutable input formats, no annotations, and no output schema, the description is thin. An agent cannot tell which payload format to choose, how to set the window/threshold knobs, or what the response contains.

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 coverage is 0% across 16 parameters, and the description explains none of them. It only indirectly implies the 'payments' array via 'caller-supplied payment events' and the threshold/window parameters (velocityCountThreshold, chargebackWindowDays, etc.) and the four alternative payload formats (csv/json/text/file/files) go 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 and resource ('Detect suspicious combinations of caller-supplied payment events') and names three concrete pattern types (declines-then-success, instrument churn, billing/shipping mismatch), which clearly separates it from refund-abuse, chargeback, and velocity siblings. It stops short of explicitly naming an alternative tool, so it is clear but not fully differentiated.

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 'caller-supplied payment events' implies the agent must supply data rather than have the server fetch it, and the 'not confirmed fraud' caveat hints at how to interpret results. However, there is no explicit when-to-use versus when-to-use-a-sibling guidance and no stated prerequisites for data volume or fields needed to trigger each pattern type.

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