Skip to main content
Glama

BRAINIAC E-commerce Fraud & Order Risk

Analyze shipping-address patterns

ecommerce-fraud_shipping-address-risk-analyze

Compare supplied shipping addresses across orders. A shared address needs at least three orders and two customers. Several addresses for one customer are a separate indicator. A missing address is not a fraud finding. Price $0.04 USDC. POST /api/v1/ecommerce-fraud/shipping-address-risk-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_shipping-address-risk-analyze"
  }
}

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 full burden and does disclose meaningful operational behavior: the $0.04 USDC price, the POST endpoint, and that unpaid calls return 402 and do not execute. It also reveals the detection rules applied, though it omits whether results are advisory scores or definitive flags.

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?

Five short, front-loaded sentences with no filler; the detection logic comes before the pricing and transport details. The telegraphic style borders on note-form, but every sentence contributes information.

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?

For a seven-parameter tool with nested objects, no output schema, and no annotations, the description is too thin: it never explains how to supply data via orders versus csv/json/text/file, what window means, or what the response contains. Only the scoring rules and payment behavior are adequately covered.

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 seven parameters, including five alternative input channels (csv, file, json, text, orders) and a nested rules object, yet the description explains none of them. The references to 'three orders and two customers' hint at the rules thresholds but leave the input-mode choice and the window parameter completely 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 specific verb and resource: 'Compare supplied shipping addresses across orders', which clearly differentiates it from the velocity, card-testing, and promotion siblings. It doesn't name an alternative tool, but the domain-specific framing is enough to identify it without opening the schema.

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?

The detection thresholds (three orders, two customers) and the explicit non-finding for missing addresses give useful context about what this tool will and won't report. However, it never states when to choose this over the other fraud analyzers or what preconditions the input data must satisfy, so selection guidance is only implied.

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