Skip to main content
Glama

BRAINIAC Fraud & Transaction Security

Analyze chargeback patterns

fraud-signals_chargeback-pattern-analyze

Analyze recurring chargeback/dispute patterns from caller-supplied payment records. Elevated rates are indicators, not confirmed fraud. Price $0.04 USDC. POST /api/v1/fraud-signals/chargeback-pattern-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_chargeback-pattern-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 but does disclose useful behavior: pricing at $0.04 USDC, the POST endpoint, and that unpaid calls return 402 and do not run. It also correctly frames results as indicators rather than confirmed fraud. However, it omits prerequisites such as minimum record counts, required identity/payment fields, authentication, and whether results are deterministic.

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?

The description is four compact sentences with the purpose front-loaded, followed by the interpretive caveat, price, endpoint, and payment behavior. Every sentence carries information and there is no filler, though the ordering could surface the input expectation earlier.

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?

This is a complex tool with 16 parameters, nested objects, no output schema, and no annotations, so the description needs to do more. It does not explain acceptable input formats, which datasets are required for meaningful analysis, or what the response contains, leaving significant gaps for an agent trying to invoke it correctly.

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 alternate input channels (csv, json, text, file, files) and several nested arrays with many fields. The description only vaguely says records are caller-supplied and does not explain which input parameter to use, the meaning of thresholds like chargebackWindowDays or velocityCountThreshold, or what record types are required.

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 states a specific verb and resource – analyzing recurring chargeback/dispute patterns from caller-supplied payment records – which distinguishes it from siblings like transaction velocity or refund abuse analysis. It does not explicitly name the sibling tools it replaces, but the resource focus is clear enough for an agent to differentiate.

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 explicit when-to-use or when-not-to-use guidance. The description only notes that records are caller-supplied and that elevated rates are indicators rather than confirmed fraud, leaving the agent to infer when this tool should be selected over the seven sibling fraud-signal tools.

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