Skip to main content
Glama

pep_tiered_risk_assessor

Read-onlyIdempotent

[Politically exposed persons tiered risk engine & 12-month cooling-off auditor. Deterministic calculation, read-only, side-effect free]. Audits PEP status under Regulation (EU) 2024/1624 Article 28 across 5 tiers, evaluating the statutory 12-month post-office cooling-off period and senior management approval requirements. Usage: Use this tool to verify PEP status, calculate elapsed time since leaving public office, and determine mandatory source of wealth audits. Returns: JSON object with { personFullName: string, isPepActive: boolean, pepCategoryTier: string, coolingOffPeriodStatus: object, mandatoryComplianceObligations: 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": {
      "personFullName": "<personFullName>",
      "countryOfPublicFunctionIso2": "<countryOfPublicFunctionIso2>",
      "roleCategory": "<roleCategory>",
      "isCurrentlyInOffice": "<isCurrentlyInOffice>"
    },
    "name": "pep_tiered_risk_assessor"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleCategoryYesCategorization of the prominent public function ex 6AMLD Article 24
personFullNameYesFull legal name of the individual
dateLeftOfficeIsoNoISO date (YYYY-MM-DD) when public office was vacated
isCurrentlyInOfficeYesWhether the person currently occupies the position
relationshipDescriptionNoNature of family tie or business partnership for Tier 4/5 PEPs
countryOfPublicFunctionIso2YesCountry where the public office was exercised
holdsBeneficialOwnershipOver25PercentNoWhether PEP holds >= 25% shareholding in client company

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 restates that as 'deterministic calculation, read-only, side-effect free' — partly redundant. Beyond that, it adds genuinely new behavioral context: the applicable regulation and article, the five-tier scheme, evaluation of the 12-month cooling-off window, and the senior-management-approval obligation. It does not cover edge cases such as a missing dateLeftOfficeIso.

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 header front-loads the tool's nature, followed by a Usage line and a Returns line — a clean, scannable structure. The bracketed block partially duplicates the annotations, costing a little space, but nothing is verbose or padded.

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 present, the description compensates by naming the returned JSON keys (personFullName, isPepActive, pepCategoryTier, coolingOffPeriodStatus, mandatoryComplianceObligations). Combined with a fully documented 7-parameter schema and read-only annotations, this is nearly complete, though it omits conditional parameter requirements such as relationshipDescription for Tier 4/5 PEPs.

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 a documented enum for roleCategory and per-field descriptions, so the schema carries the parameter burden. The description adds no field-level meaning beyond what is already structured, which is the baseline-3 case.

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?

The description states a specific verb and resource — auditing PEP status and computing the statutory cooling-off period under Regulation (EU) 2024/1624 Article 28 — and scopes it to 5 tiers. This is clearly distinguishable from siblings such as aml_customer_risk_scorer or high_risk_jurisdiction_screener, which address different compliance questions.

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' sentence names three concrete jobs (verify PEP status, calculate elapsed time since office, determine mandatory source of wealth audits), which gives an agent a clear trigger. It does not, however, state when NOT to use it or point to an alternative tool for adjacent risk scoring.

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