Skip to main content
Glama

BRAINIAC AML Monitoring Thresholds & Deadlines

Cash structuring heuristic

aml-monitoring_structuring-detect
Read-onlyIdempotent

Flag repeated just-below-threshold cash deposits as a structuring heuristic for analyst review. Price $0.03 USDC. POST /api/v1/aml-monitoring/structuring-detect. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "transactions": "<transactions>"
    },
    "name": "aml-monitoring_structuring-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNoparams, object. Required.
transactionsYestransactions, array. Required.

Output Schema

NameRequiredDescriptionDefault
alertsNoalerts. Array.
paramsNoparams. Object.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations' read-only, idempotent, open-world, and non-destructive profile, the description discloses a price of $0.03 USDC and states that unpaid calls return x402 payment terms without running. This adds useful invocation behavior, though it does not discuss rate limits or detection logic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and then adds only the payment cost, endpoint, and unpaid-call behavior. Every sentence is short and relevant to invoking or understanding the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a rich input schema, an output schema, and annotations, the description supplies the core purpose, endpoint, and payment behavior. It is largely complete for invocation, though comparative usage guidance is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents transactions, params, defaults, and ranges. The description's 'just-below-threshold' wording adds some domain context but does not map to specific parameters such as lowerRatio, minCount, windowDays, or minTotalRatio.

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 ('Flag'), resource ('repeated just-below-threshold cash deposits'), and analytic purpose ('structuring heuristic for analyst review'). It is clear what the tool detects, but it does not explicitly differentiate the scenario from sibling detection tools.

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 description implies use for structuring review by analysts and mentions the payment requirement, but it gives no explicit when-to-use, when-not-to-use, or comparison to alternatives such as rapid-movement-detect or ctr-aggregate.

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