Skip to main content
Glama

BRAINIAC Fraud & Transaction Security

Detect refund-abuse patterns

fraud-signals_refund-abuse-pattern-detect

Detect abnormal refund frequency and amount ratios from caller-supplied payment histories. Refund rate alone is not confirmed fraud. Price $0.04 USDC. POST /api/v1/fraud-signals/refund-abuse-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_refund-abuse-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 supplied, the description carries the full burden and does disclose meaningful operational facts: a $0.04 USDC price, the POST endpoint, and that unpaid calls return 402 and do not execute. It does not describe output shape, latency, or how the internal thresholds affect the verdict.

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 the core purpose, followed by the interpretive caveat and then the transactional details. Nothing is padded, though the endpoint path and price could arguably be moved after any input guidance.

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 complex tool with 16 parameters, nested file objects, no annotations, and no output schema, the description is far too thin. It says nothing about which input form to use, how the configurable windows interact, or what the caller receives back, leaving the agent unable to call it correctly without guessing.

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?

There are 16 parameters with 0% schema description coverage and deeply nested objects, yet the description only hints that payment histories are the input. It never explains the roles of csv/json/text/file/files, asOf, or the six window and threshold parameters such as refundWindowDays and velocityCountThreshold, so the agent must guess at nearly all inputs.

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 gives a specific verb and resource: detecting abnormal refund frequency and amount ratios from caller-supplied payment histories. It implicitly distinguishes itself from chargeback or velocity siblings by focusing on refund behavior, but never names an alternative to make the distinction explicit.

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?

Usage is only implied by the phrase 'caller-supplied payment histories,' and the caution 'Refund rate alone is not confirmed fraud' guides interpretation of results. There is no statement of when to prefer this over the chargeback, invoice, or velocity siblings, and no prerequisites for input data are given.

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