Skip to main content
Glama

aml_customer_risk_scorer

Read-onlyIdempotent

[Single AML rulebook customer due diligence risk scorer. Deterministic calculation, read-only, side-effect free]. Calculates customer risk tier (Low, Medium, High, Unacceptable) under Regulation (EU) 2024/1624 based on entity structure, geography, delivery channels, and volume, specifying mandatory EDD controls. Usage: Pass customer onboarding attributes to determine mandatory CDD vs EDD requirements and senior management approval triggers. Returns: JSON object with { customerName: string, riskScore: number, riskTier: string, dueDiligenceLevelRequired: string, mandatoryComplianceMeasures: array, riskFactorBreakdown: object }.

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": {
      "customerName": "<customerName>",
      "customerType": "<customerType>",
      "jurisdictionCountryIso2": "<jurisdictionCountryIso2>",
      "deliveryChannel": "<deliveryChannel>",
      "expectedAnnualTransactionVolumeEur": "<expectedAnnualTransactionVolumeEur>"
    },
    "name": "aml_customer_risk_scorer"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerNameYesCustomer corporate legal name or individual full name
customerTypeYesCustomer legal and entity categorization
deliveryChannelYesClient onboarding and interaction channel
isCashIntensiveBusinessNoWhether business operates in cash-heavy sectors (dining, gambling, art, foreign exchange)
jurisdictionCountryIso2Yes2-letter ISO country code of customer incorporation or primary residence
isHighNetWorthIndividualNoWhether individual customer holds liquid assets exceeding €1M
isCryptoVirtualAssetProviderNoWhether entity is a Virtual Asset Service Provider (VASP/CASP)
expectedAnnualTransactionVolumeEurYesAnticipated annual transaction volume in EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 is consistent, adding 'deterministic calculation' and 'side-effect free' so the agent knows repeated calls are safe. It also discloses the output shape, which is real behavioral context. It does not cover permissions, jurisdiction coverage limits, or how borderline scores are resolved, which keeps it below a 5.

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?

Front-loaded with the purpose, then Usage, then Returns, which is good structure and easy to scan. The bracketed header slightly repeats what annotations already say (read-only, deterministic), but it is compact and no sentence is 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 8 parameters, 5 required, and no output schema, the description compensates by spelling out the returned JSON fields and the regulatory basis. An agent can call it correctly from this. Remaining gaps, such as score thresholds or handling of invalid ISO codes, are minor but not covered.

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%, with enums and per-field descriptions, so the schema carries parameter meaning almost entirely. The description adds a useful aggregation by naming the four risk pillars (entity structure, geography, delivery channels, volume) that the inputs feed into, but it does not map individual parameters to weighting or thresholds. Baseline 3 is appropriate.

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: calculates a customer risk tier (Low/Medium/High/Unacceptable) under Regulation (EU) 2024/1624 from entity structure, geography, channels and volume, and emits mandatory EDD controls. That is far more specific than the name alone. It does not explicitly name or contrast a sibling such as aml_suspicious_activity_screener, so the differentiation is implicit in the word 'customer due diligence' rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Usage' line places the tool firmly in the onboarding flow: pass onboarding attributes to get mandatory CDD vs EDD requirements and senior-management approval triggers. That is clear when-to-use context. It gives no when-not conditions or alternative tools, so it stops short of the top score.

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