Skip to main content
Glama

BRAINIAC E-commerce Fraud & Order Risk

Report order-risk indicators

ecommerce-fraud_investigation-report

Combine supplied amount, card, address, promotion, refund, and velocity patterns. Review means two or more indicators. The report does not confirm fraud, process a payment, or block an order. Price $0.12 USDC. POST /api/v1/ecommerce-fraud/investigation-report. 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_investigation-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
rulesNo
ordersNo
windowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that the report does not confirm fraud, process payment, or block orders (effectively read-only), states the price ($0.12 USDC), the POST endpoint, and that unpaid calls return 402 and do not execute. It does not cover rate limits 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?

Short, front-loaded sentences with no filler; the core capability comes first, followed by scope disclaimers and payment details. Slightly fragmented by mixing pricing and endpoint metadata into the same block as behavioral scope.

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?

This is a complex tool (7 params, nested order objects, no annotations, no output schema), yet the description omits how inputs may be supplied, how the rules thresholds and window affect results, and any indication of return structure. An agent has enough to know the tool's purpose but not enough to call it confidently.

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% for 7 parameters, including nested objects, so the description must compensate. It alludes to order fields (amount, card, address, promo, velocity) but says nothing about the csv/json/text/file input alternatives, the rules object (orders, quantity, smallAmount) or the window parameter, leaving most parameters 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?

States a concrete verb and resource: it combines several risk signals (amount, card, address, promotion, refund, velocity) into one investigation report. The signal list implicitly distinguishes it from the single-signal sibling detectors, though it never names or explicitly contrasts with them.

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?

'Review means two or more indicators' defines the threshold the report applies internally, not when an agent should pick this tool over the per-signal detectors. Usage is implied by the aggregate nature of the tool, but no explicit when-to-use/when-not guidance or alternative routing is provided.

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