Skip to main content
Glama

BRAINIAC E-commerce Fraud & Order Risk

Analyze order velocity

ecommerce-fraud_order-velocity-analyze

Count supplied orders for the same customer, IP, or card. With a minute window and timestamps, the orders must fall inside that window. Otherwise they are compared on the same calendar day. Fewer than three orders is not a pattern. Price $0.05 USDC. POST /api/v1/ecommerce-fraud/order-velocity-analyze. 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_order-velocity-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
rulesNo
ordersNo
windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 disclose several non-obvious behaviors: the $0.05 USDC charge, the 402 response on unpaid calls with no execution, and the window-vs-calendar-day comparison rule. It omits return shape and how malformed or partial order records are handled, which keeps it short of a 5.

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?

Front-loaded with the core behavior, then the window rule, threshold, price, and endpoint. Every sentence carries information; the raw endpoint path and payment note are operational rather than descriptive but still earn their place for a paid tool.

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 paid, POST-based analyzer with seven parameters, zero schema descriptions, nested objects, and no output schema, the description covers timing logic well but leaves the input contract largely unexplained. An agent still cannot confidently choose between passing orders, csv, json, text, or a file upload based on the definition 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 coverage is 0% across 7 parameters including nested objects, and the description explains only the window parameter and which order fields are used for grouping. The five mutually exclusive input modes (csv, file, json, text, orders) and the rules object (orders minimum, quantity, smallAmount) are never mentioned, leaving the caller to guess which input to supply.

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?

Opens with a specific verb and resource: counting supplied orders grouped by customer, IP, or card to surface a velocity pattern. It is clear what the tool does, but it never names or contrasts the overlapping siblings such as card-testing-pattern-detect or bulk-order-abuse-detect, so sibling differentiation is left to the caller.

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?

Usage is implied by the window semantics and the 'fewer than three orders is not a pattern' threshold, which tells the agent what qualifies as a hit. There is no explicit statement of when to prefer this over the other fraud analyzers, and no prerequisites or exclusions.

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