Skip to main content
Glama

BRAINIAC E-commerce Fraud & Order Risk

Detect suspicious order patterns

ecommerce-fraud_suspicious-order-detect

Compare supplied amounts with a Tukey fence when 8 orders share a currency, and with a customer's own median when that customer has at least four amounts. A new address counts only after earlier orders. One signal is an indicator, not confirmed fraud. Price $0.05 USDC. POST /api/v1/ecommerce-fraud/suspicious-order-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_suspicious-order-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, and it does disclose useful traits: a single signal is an indicator not confirmed fraud, the call costs $0.05 USDC, it is a POST to a named endpoint, and unpaid calls return 402 without executing. It does not say whether anything is persisted, what happens on partial or malformed input, 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?

Three compact sentences with the decision logic front-loaded, followed by the pricing/payment constraint. No filler, though the algorithmic detail arrives before any plain statement of what the tool returns.

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 7-parameter, nested-schema tool with no annotations and no output schema, the description explains the scoring logic and payment gating but omits input-format selection and any indication of return shape. An agent can form the call but must guess at payload structure and results.

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 and a rules object, so the description must compensate. It only hints at semantics for amount, currency, customer, and address ordering, leaving the four input-format parameters (csv, json, text, file), the window parameter, and the rules thresholds entirely 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 states a concrete operation – comparing supplied amounts against a Tukey fence and a per-customer median – so the agent knows this is an amount-anomaly check on order data. It never names a sibling or explicitly scopes itself against bulk-abuse, velocity, or card-testing tools, so differentiation is left to inference.

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 the conditions under which each signal fires (8 orders sharing a currency; a customer with at least four amounts; a new address after earlier orders), which tells the agent what input composition is needed. It offers no when-not guidance or routing to sibling detectors for velocity, promo, or refund abuse.

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