Skip to main content
Glama

BRAINIAC AML Monitoring Thresholds & Deadlines

CTR cash aggregation

aml-monitoring_ctr-aggregate
Read-onlyIdempotent

Aggregate cash-in and cash-out per person per US business day and list totals that trigger a Currency Transaction Report. Price $0.03 USDC. POST /api/v1/aml-monitoring/ctr-aggregate. 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_ctr-aggregate"
  }
}

Input Schema

NameRequiredDescriptionDefault
regimeNoregime, string, one of US_CTR, custom. Required.US_CTR
nearRatioNonearRatio, number, from 0.1 to 1. Required.
thresholdNothreshold, integer, from any to 9007199254740991. Optional.
businessDaysNobusinessDays, object. Required.
transactionsYestransactions, array. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
thresholdNothreshold. Number.
reportableNoreportable. Array.
limitationsNolimitations. Array.
nearThresholdNonearThreshold. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description earns credit for disclosing the paid-gate behavior ('an unpaid call returns the x402 payment terms and does not run') and the $0.03 USDC price, which annotations cannot express. It still says nothing about response size, batching limits, or how many transactions are practical per call.

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?

Three tight sentences: what it does first, then cost, then endpoint, then the payment failure mode. No filler and nothing buried behind later clauses.

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?

For a nested-object tool with an output schema and full annotations, the description supplies the missing non-schema facts an agent needs: price, endpoint, and unpaid-call behavior. The main residual gap is that nearRatio and the US_CTR vs custom regime choice are left entirely unexplained for what is otherwise a compliance-sensitive calculation.

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

Parameters4/5

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

Schema coverage is 100%, so the schema carries the semantics and baseline 3 applies. The description adds a little mapping value by tying 'per person' to personIds and 'per US business day' to businessDays, and the CTR-trigger framing gives threshold/nearRatio operational meaning the schema's mechanical 'number, from 0.1 to 1' wording does not.

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 uses a specific verb ('Aggregate') with a precisely scoped resource ('cash-in and cash-out per person per US business day') and adds the CTR-trigger output. That scope is distinctive enough to separate it from the detection-oriented siblings, though it never names an alternative tool outright.

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 only implied: the CTR framing tells an agent this is the aggregation path for currency-transaction-report screening, but there is no explicit 'use this when' or 'use X instead' guidance against the sibling detection tools. The payment caveat is a calling precondition, not a when-to-use rule.

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