Skip to main content
Glama

high_risk_jurisdiction_screener

Read-onlyIdempotent

[EU high-risk third country screener & FATF blacklist auditor. Deterministic check, read-only, side-effect free]. Screens counterparties against Commission Delegated Regulation (EU) 2016/1675 and FATF lists, enforcing mandatory Article 29 Enhanced Due Diligence and correspondent banking prohibitions. Usage: Screen any counterparty jurisdiction to detect strategic anti-money laundering deficiencies and determine required countermeasures. Returns: JSON object with { countryIso2: string, countryName: string, isHighRiskThirdCountry: boolean, riskCategory: string, mandatoryEddCountermeasures: array, correspondentBankingProhibition: boolean }.

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": {
      "countryIso2": "<countryIso2>"
    },
    "name": "high_risk_jurisdiction_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryIso2Yes2-letter ISO country code of counterparty entity or financial institution
transactionTypeNoNature of financial transaction
counterpartyInstitutionBicNoSWIFT/BIC code of counterparty bank

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; the description reinforces this with "deterministic check, read-only, side-effect free", which is consistent rather than redundant filler. It goes further by disclosing the enforcement consequence (mandatory Article 29 EDD, correspondent banking prohibitions) and enumerating the returned JSON fields, though it says nothing about error behavior for an unrecognized ISO code.

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 bracketed preamble front-loads the domain, safety profile, and legal basis, followed by usage and return blocks — a scannable structure. The "Usage: Screen any counterparty jurisdiction..." line partially restates the opening sentence, so a small amount of text does not earn its place.

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 no output schema, the description compensates by enumerating the returned fields (countryIso2, isHighRiskThirdCountry, riskCategory, mandatoryEddCountermeasures, correspondentBankingProhibition), which is exactly what an agent needs to plan downstream use. Minor gaps remain around how optional parameters shape the result and what is returned for a non-listed jurisdiction.

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 countryIso2, transactionType, and counterpartyInstitutionBic are already documented in the schema; baseline 3 applies. The description adds no meaning beyond it — it does not explain how transactionType changes the countermeasures returned or why the BIC is needed.

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: screens counterparties against Commission Delegated Regulation (EU) 2016/1675 and FATF lists, with the legal basis and the EDD/prohibition consequences named. It is clearly a jurisdiction-screen rather than a customer or PEP scorer, so it is distinguishable from AML siblings, but it never names an adjacent tool (e.g. a customer risk scorer) to draw the boundary explicitly.

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?

"Screen any counterparty jurisdiction to detect strategic anti-money laundering deficiencies and determine required countermeasures" gives clear conditions for use. There is no explicit when-not guidance, no statement about what happens for non-listed or invalid jurisdictions, and no named alternative for cases this tool does not cover.

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