Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

screen_global_sanctions_and_kyb

Read-onlyIdempotent

Screen corporate legal entities and individuals against global sanctions lists, GLEIF LEI registry, and PEP databases for KYB and AML compliance.

Instructions

Screen corporate legal entities and individuals against the official GLEIF Legal Entity Identifier (LEI) registry, OFAC SDN, UN Security Council, EU consolidated sanctions lists, and Politically Exposed Persons (PEP) databases.

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": {
      "entities": "<entities>"
    },
    "name": "screen_global_sanctions_and_kyb"
  }
}

Input Schema

NameRequiredDescriptionDefault
entitiesYesOrganization names or individual full names to screen for KYB/AML compliance.
maxResultsNoMaximum number of KYB and sanctions screening records to return.
includeGleifLeiNoWhether to resolve official GLEIF Legal Entity Identifier (LEI) registration records.
includeSanctionsMatchNoWhether to check OFAC, UN, EU, and PEP sanctions watchlists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value by naming the exact external registries consulted, but says nothing about match semantics (fuzzy vs exact name matching), false-positive handling, or whether results are candidate hits rather than determinations — material behavior for a screening tool.

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?

A single front-loaded sentence with no filler; the verb and resource lead and the source enumeration follows. It is efficient, though it largely restates the annotation title's list of registries, so a small amount of content is redundant with structured metadata.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description never indicates what a screening response contains — match confidence, matched-entity details, or how multiple input entities map to results. For a compliance-screening tool with four parameters and named external data sources, that return-value gap is the main incompleteness.

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% and every parameter (entities, maxResults, includeGleifLei, includeSanctionsMatch) carries its own description with defaults and bounds. The description's list enumeration loosely explains what the two boolean toggles control, but adds no syntax or formatting detail beyond the schema, so the baseline 3 applies.

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?

Opens with a specific verb ('Screen') and a precise resource ('corporate legal entities and individuals'), then enumerates the exact data sources checked (GLEIF LEI, OFAC SDN, UN, EU consolidated, PEP). That resource specificity naturally separates it from the nearest sibling, screen_wallet_aml_risk, but the description never states the distinction explicitly, so it stops short of a 5.

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 compliance framing ('KYB/AML') in the schema and the enumerated watchlists imply onboarding/due-diligence use, but the description itself gives no explicit when-to-use trigger, no prerequisites, and no routing guidance to alternatives such as the wallet-screening sibling. Usage must be inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.