Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP

global_sanctions_pep_gleif_kyb_screener

Read-onlyIdempotent

Global Corporate KYB GLEIF LEI Sanctions API: Global Corporate KYB verification, official GLEIF Legal Entity Identifier (LEI) search, and international sanctions watchlist screening.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "global_sanctions_pep_gleif_kyb_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of entity records to return (1-50, default: 10).
queryNoEntity name, company, applicant, or LEI code to search (e.g., "OpenAI", "Siemens", "Microsoft").OpenAI
statusNoFiling or compliance status filter (e.g., "ACTIVE", "SANCTIONED", "REGISTERED").ACTIVE
countryNoTwo-letter jurisdiction or country code (e.g., "US", "DE", "GB", "CH").US

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "default": "US",
      +  "description": "Two-letter jurisdiction or country code (e.g., \"US\", \"DE\", \"GB\", \"CH\").",
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 10,
      +  "description": "Maximum number of entity records to return (1-50, default: 10).",
      +  "type": "integer"
      +}
    • removedInput schema / properties / maxResults
      Removed value: -{
      -  "default": 10,
      -  "description": "Maximum number of structured items to extract.",
      -  "type": "integer"
      -}
    • addedInput schema / properties / query
      Added value: +{
      +  "default": "OpenAI",
      +  "description": "Entity name, company, applicant, or LEI code to search (e.g., \"OpenAI\", \"Siemens\", \"Microsoft\").",
      +  "type": "string"
      +}
    • addedInput schema / properties / status
      Added value: +{
      +  "default": "ACTIVE",
      +  "description": "Filing or compliance status filter (e.g., \"ACTIVE\", \"SANCTIONED\", \"REGISTERED\").",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

B3.3/5.0
Behavior2/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 fully covered by structured data. The description adds almost nothing beyond that: 'official GLEIF' is the one real signal (authoritative data source), but there is no mention of coverage limits, latency, auth, or what a screening result contains.

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?

Placeholder

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?

With no output schema, the description should hint at what a lookup returns (entity records, LEI codes, sanction hit flags) and it does not, leaving the agent to guess whether 'screening' means a boolean risk verdict or raw registry data. Parameters are fully covered by the schema, so the remaining gap is the result shape.

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%, with limit, query, status, and country all individually documented, so the baseline of 3 applies. The description adds no meaning beyond the schema – it never explains, for example, that country scopes the jurisdiction of the entity or that status can isolate sanctioned entities.

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?

The description names a specific resource set – corporate KYB verification, GLEIF LEI lookup, and sanctions watchlist screening – so an agent can tell it is an entity-due-diligence lookup rather than a price, macro, or CVE tool. It stops short of naming any sibling or stating which of the sanctions/AML-adjacent tools to prefer, which keeps it out of 5 territory.

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?

Use is only implied by domain vocabulary: 'KYB verification' and 'sanctions watchlist screening' suggest counterparty due diligence. There is no explicit when-to-use statement, no prerequisite, and no exclusion or alternative named despite several adjacent sanctions and risk screeners in the sibling list.

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.