Skip to main content
Glama

BRAINIAC E-commerce Fraud & Order Risk

Detect promotion patterns

ecommerce-fraud_promotion-abuse-detect

Report a promotion code only when the same customer uses it on at least three supplied orders, or when the same code and address appear for at least two customers. One use is not abuse. Price $0.04 USDC. POST /api/v1/ecommerce-fraud/promotion-abuse-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_promotion-abuse-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
rulesNo
ordersNo
windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 safety burden and does meaningful work: it discloses cost ($0.04 USDC), the HTTP transport, and that unpaid calls return 402 without executing. It stops short of stating whether the operation is read-only, what the response contains, or any rate/timeout limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The detection rule is front-loaded, the exclusion and billing/transport facts follow in short declarative sentences, and nothing is padding. Every clause conveys information the agent needs before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 7 parameters, nested order objects, no output schema, and no annotations, the description is thin on the input contract. It covers the detection policy and payment behavior well but leaves the agent without guidance on which input mode to supply or how rules and window affect results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 7 parameters, so the description has to compensate. It explains that orders are supplied and ties the 'at least three orders' threshold to input, but never mentions the four alternate payload modes (csv, json, text, file), the rules override object, or the window parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific detection task and defines the exact conditions that constitute promotion abuse (same customer on three or more supplied orders, or same code and address across two or more customers). This is a concrete verb-plus-resource statement with an operational definition, not a restatement of the title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear positive condition for flagging and an explicit negative case ('One use is not abuse'), which steers the agent away from over-reporting. It does not, however, say when to reach for this tool versus siblings like shipping-address-risk-analyze or bulk-order-abuse-detect, leaving the choice to the agent.

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