Skip to main content
Glama

BRAINIAC E-commerce Fraud & Order Risk

Detect bulk-order patterns

ecommerce-fraud_bulk-order-abuse-detect

Flag a shipping address only when it appears on at least three supplied orders. Combined quantity is compared with a caller rule across those orders. One large order is not a bulk pattern. Price $0.04 USDC. POST /api/v1/ecommerce-fraud/bulk-order-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_bulk-order-abuse-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
rulesNo
ordersNo
windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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. It discloses the detection rule (3+ orders per address, quantity aggregated against a caller rule), the cost ($0.04 USDC), and that unpaid calls return 402 without running — all genuinely useful. It says nothing about the response shape, address normalization, or what happens when the alternate input formats (csv/json/text/file) are supplied, leaving meaningful behavioral gaps.

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?

Short declarative sentences with the gating condition front-loaded and zero filler. The endpoint and pricing lines are operational rather than descriptive, but they are brief and placed after the core rule, so they do not crowd out the substance.

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 a large nested schema, no annotations, and no output schema, the description covers the core detection logic and payment failure mode. It is not complete: input-channel selection, the rules object semantics, and the window parameter are all unexplained, which matters given 0% schema coverage.

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 a nested orders array and a nested rules object, so the description must compensate. It only gestures at 'supplied orders' and 'caller rule', explaining neither the four mutually alternative input channels (orders, csv, json, text, file) nor the rules sub-fields (orders/quantity/smallAmount) or the window. An agent could not pick the right input mode from this text alone.

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+resource+condition: 'Flag a shipping address only when it appears on at least three supplied orders.' That is concrete and distinguishable from a single-order or velocity check. It stops short of naming a sibling such as shipping-address-risk-analyze, so it earns a 4 rather than a 5.

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 gives one useful exclusion ('One large order is not a bulk pattern'), which tells the agent this is not a single-order anomaly check. It never says when to prefer the address-risk or velocity siblings, and the three-order threshold excludes the two-order case without guidance on where that belongs.

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