Skip to main content
Glama

BRAINIAC E-commerce Fraud & Order Risk

Detect card-testing patterns

ecommerce-fraud_card-testing-pattern-detect

Group supplied card fingerprints. Three or more declines on one fingerprint, or three or more cards for one customer, are indicators. A small-amount rule is used only when the caller supplies it. No payment is retried. Price $0.05 USDC. POST /api/v1/ecommerce-fraud/card-testing-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": "ecommerce-fraud_card-testing-pattern-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
rulesNo
ordersNo
windowNo

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, the description carries the full burden and does meaningful work: it discloses the cost ($0.05 USDC), the payment gate (unpaid calls return 402 and do not run), and that no payment is retried. It omits auth details and the shape of the result, but the safety and billing profile is unusually well covered for an unannotated tool.

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?

Five short sentences, front-loaded with the core action and thresholds, with billing and endpoint facts trailing. Nothing is padding, though a few fragments ("Group supplied card fingerprints") are terse enough to be slightly ambiguous about what grouping means.

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 nested objects, five mutually overlapping input formats, and no output schema, yet the description never explains input precedence or what the caller receives back. The payment and rule semantics are covered, but an agent cannot reliably construct a valid call from this alone.

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 7 parameters, including nested order objects, so the description must compensate and largely does not. It hints at rules.smallAmount and the concept of card fingerprints, but says nothing about how csv, json, text, file, and orders trade off, nor what window or rules.orders/quantity mean.

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 opens with a concrete verb and resource ("Group supplied card fingerprints") and names the detection heuristics used, which lets an agent distinguish card-testing from refund, promotion, or velocity analysis siblings. It stops short of explicitly contrasting with those siblings, 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 thresholds (three declines on one fingerprint, three cards per customer) imply when the tool is applicable, and the small-amount rule is explicitly scoped to caller-supplied input. However, there is no explicit statement of when to choose this over the other fraud detectors or what prerequisites the input must meet.

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