Skip to main content
Glama

BRAINIAC E-commerce Fraud & Order Risk

Detect refund patterns

ecommerce-fraud_refund-abuse-pattern-detect

Count supplied orders whose status is refunded. A customer needs at least three refunds before a repeat pattern is reported. A single refund is not treated as abuse. Price $0.04 USDC. POST /api/v1/ecommerce-fraud/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": "ecommerce-fraud_refund-abuse-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.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully reveals cost ($0.04 USDC) and that unpaid calls return 402 without running, which an agent needs before invoking a paid endpoint. It does not disclose whether the operation is read-only, whether submitted order data is retained, or what the response contains.

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 detection logic, then threshold interpretation, then billing and transport details. Every sentence carries information; the endpoint string is arguably redundant but is defensible for a paid API call.

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?

The tool has a rich nested schema, no output schema, and no annotations, so the description must do more work. It covers the detection rule and payment behavior but omits how to feed orders (csv vs json vs file), what window controls, and what the returned report looks like.

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 seven parameters, including a nested file object, a rules object with orders/quantity/smallAmount, an orders array of per-order fields, and a window value. The description mentions only 'supplied orders' and the three-refund threshold, leaving input format (csv/json/text/file) and the window/rules semantics undocumented.

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: count supplied orders with refunded status and report repeat refund patterns. That is specific enough for an agent to distinguish this refund-focused detector from promotion or bulk-order siblings, although it never names an alternative explicitly.

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?

It states the rule of thumb (three or more refunds per customer to constitute a pattern, a single refund is not abuse), which tells the agent when results will actually fire. It does not say when to choose this tool over ecommerce-fraud_promotion-abuse-detect or suspicious-order-detect, so routing guidance is only implied.

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