Skip to main content
Glama

ultimate_beneficial_owner_audit

Read-onlyIdempotent

[Deterministic AML UBO ownership cascade & PEP audit. Pure calculation, read-only, side-effect free]. Calculates multi-tier corporate shareholding chains to identify Ultimate Beneficial Owners (UBO) exceeding statutory 25% ownership or control thresholds under 5AMLD/6AMLD (Directive (EU) 2018/843) and D.Lgs. 231/2007, flagging Politically Exposed Persons (PEPs) and opaque jurisdictions. Usage: Use this tool for statutory AML/KYC onboarding, corporate governance audits, and sanction ownership screening. Returns: JSON object with { targetCompanyName: string, beneficialOwners: array, controlBySeniorManagementRequired: boolean, amlRiskScore: number, amlRiskLevel: string, redFlags: array, complianceNotes: string }.

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": {
      "targetCompanyName": "<targetCompanyName>",
      "companyVatOrId": "<companyVatOrId>",
      "shareholders": "<shareholders>"
    },
    "name": "ultimate_beneficial_owner_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
shareholdersYesShareholding structure nodes for direct and indirect cascading ownership calculation
companyVatOrIdYesTax code, VAT number, or national registration ID
targetCompanyNameYesLegal name of subject enterprise
legalRepresentativeNameNoName of administrator or legal representative
fallbackToLegalRepresentativeNoWhether to fallback to senior executive management if no UBO exceeds 25%

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description still adds value by asserting the calculation is deterministic, pure, and side-effect free, and by disclosing the regulatory ruleset it applies and the PEP/opaque-jurisdiction flagging behavior. It does not address authorization requirements, input size limits, or handling of inconsistent ownership data.

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?

The definition is front-loaded with a bracketed one-line identity, then purpose, then Usage, then Returns. Every sentence carries information and the labeled sections make scanning trivial; nothing is redundant filler.

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 complex multi-tier ownership calculation, the description covers purpose, legal basis, triggering use cases, and enumerates the return fields even though no output schema exists. The remaining gap is the fallback-to-legal-representative mechanism, which is central to the tool's result but only implied via the returned controlBySeniorManagementRequired field.

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 the baseline is 3; every parameter including the nested indirect holdings chain is already documented. The description adds domain meaning (the 25% control threshold, what a PEP is, the senior-management fallback implied by controlBySeniorManagementRequired) but never maps that meaning explicitly to fallbackToLegalRepresentative or legalRepresentativeName.

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 names a specific verb and resource: it calculates multi-tier shareholding chains to identify Ultimate Beneficial Owners above the 25% statutory threshold. It further anchors the purpose to named legal frameworks (5AMLD/6AMLD, D.Lgs. 231/2007), which distinguishes it in kind from the sibling scoring/screening tools such as aml_customer_risk_scorer and aml_suspicious_activity_screener.

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?

A dedicated 'Usage' line lists concrete triggering contexts: statutory AML/KYC onboarding, corporate governance audits, and sanction ownership screening. It does not state when NOT to use it or name an alternative tool for adjacent needs, so the routing guidance is clear but not exhaustive.

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