Skip to main content
Glama

BRAINIAC AML Monitoring Thresholds & Deadlines

Rapid pass-through detection

aml-monitoring_rapid-movement-detect
Read-onlyIdempotent

Detect credits quickly followed by similar-sized debits as a money-mule pass-through indicator on caller data when monitoring transactions or an AML deadline. Call with accountId and transactions; optional params. Returns accountId, matches, summary, and params (matches includes creditId, debitIds, creditAmount, debitTotal, ratio, hoursToExit). HTTP 200 with status complete, partial, or failed is charged at the full listed price. HTTP 4xx/5xx are not charged. Keywords: anti-money-laundering, AML screen, when monitoring transactions or an AML deadline, accountId, transactions, params, matches, summary, Rapid pass-through detection, rapid movement detect.

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": {
      "accountId": "<accountId>",
      "transactions": "<transactions>"
    },
    "name": "aml-monitoring_rapid-movement-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNoparams, object. Required.
accountIdYesaccountId, string, length 1 to 120. Required.
transactionsYestransactions, array. Required.

Output Schema

NameRequiredDescriptionDefault
paramsNoparams. Object.
matchesNomatches. Array.
sourcesNosources. Array.
summaryNosummary. Object.
accountIdNoaccountId. String.
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?

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds genuinely new context the annotations do not: billing is charged on HTTP 200 regardless of complete/partial/failed status, while 4xx/5xx are free — useful for an agent deciding whether to retry or batch.

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

Conciseness3/5

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

The opening two sentences are front-loaded and efficient, but the description then repeats 'when monitoring transactions or an AML deadline' verbatim and appends a long 'Keywords:' dump restating the tool name, parameters, and return fields. That trailing list adds bulk without information.

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?

An output schema exists, so return-field enumeration is redundant but harmless. Required inputs, defaults, and the charging model are all covered; only the meaning of a 'partial' status result is left unexplained for a tool with nested input and multiple sub-parameters.

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 coverage is 100%, so the schema already documents accountId, transactions, and every params sub-field with ranges and defaults. The description only restates 'Call with accountId and transactions; optional params' without adding meaning such as what minOutRatio or maxHours actually control.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — detecting credits followed by similar-sized debits as a money-mule pass-through indicator — with the precise matching logic (similar-sized, quick succession) that distinguishes it from siblings like structuring-detect or ctr-aggregate.

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 trigger phrase 'when monitoring transactions or an AML deadline' gives loose context for use, but no explicit when-not conditions and no named alternative tool. The agent must infer which sibling is appropriate.

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