Skip to main content
Glama

aml_suspicious_activity_screener

Read-onlyIdempotent

[AML suspicious activity indicator & national FIU filing engine. Deterministic anomaly analysis, read-only, side-effect free]. Evaluates transaction anomaly indicators (pass-through accounts, volume spikes, structuring) for mandatory STR/SAR reporting under Directive (EU) 2024/1640 Article 50 with tipping-off safeguards. Usage: Pass transaction pattern indicators to calculate suspicion score and identify the designated national FIU (UIF, TRACFIN, FIU-Germany). Returns: JSON object with { caseReference: string, suspicionScore: number, suspicionSeverity: string, isStrFilingMandatory: boolean, designatedNationalFiuAgency: object, triggeredRedFlags: array, mandatoryImmediateActions: array }.

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": {
      "caseReference": "<caseReference>",
      "reportingEntityCountryIso2": "<reportingEntityCountryIso2>",
      "transactionAmountEur": "<transactionAmountEur>",
      "anomalyIndicators": "<anomalyIndicators>"
    },
    "name": "aml_suspicious_activity_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
caseReferenceYesInternal compliance audit case reference or alert ID
anomalyIndicatorsYesRed flag anomaly indicators observed during monitoring
transactionAmountEurYesNominal transaction amount in EUR
reportingEntityCountryIso2YesCountry of the reporting obliged entity (e.g. IT, FR, DE, ES, NL)
customerDeclaredMonthlyIncomeEurNoDeclared baseline monthly income/revenue of the customer in EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with 'deterministic anomaly analysis, read-only, side-effect free', so the safety profile is unambiguous. It adds genuinely new behavioral context beyond annotations: the tipping-off safeguard constraint and the notion of 'mandatoryImmediateActions' imply follow-up obligations. It stops short of describing scoring transparency or error behavior, but for a read-only tool the bar is lower.

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?

The definition is front-loaded with a bracketed purpose summary, then a Usage sentence and a Returns enumeration, so an agent can scan it quickly. There is slight redundancy in 'read-only, side-effect free' given the annotations, but nothing is bloated or wasted.

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 5 parameters including a nested six-flag object and no output schema, the description compensates by enumerating the exact return fields, which is the key missing structured information. It covers purpose, inputs, and outputs adequately; only cross-tool routing and error handling are 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%, including per-flag descriptions inside the nested anomalyIndicators object, so the schema does the heavy lifting. The description only restates 'pass transaction pattern indicators' without adding format, threshold, or interaction meaning beyond what the schema already provides, which is the baseline-3 case.

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 and resource: it evaluates AML anomaly indicators and computes a suspicion score plus mandatory STR/SAR filing determination, and it names the regulatory basis (Directive (EU) 2024/1640 Article 50). It does not explicitly differentiate itself from the sibling aml_customer_risk_scorer, so an agent must infer the boundary between scoring a customer's risk and screening a specific transaction pattern.

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 'Usage' line tells the agent what to pass in (transaction pattern indicators) and what comes out (suspicion score and designated national FIU), which is useful invocation context. However, it never states when to use this versus aml_customer_risk_scorer or when the tool is inappropriate (e.g. pre-transaction screening vs post-alert investigation), so the guidance is implied rather than explicit.

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