Skip to main content
Glama
GMPSignal Real-Time Intelligence MCP (59 Tools)

GMPSignal Real-Time Intelligence MCP (59 Tools)

Official
by xpayrcom

global_sanctions_pep_gleif_kyb_screener

Screen global corporates for KYB, PEP and sanctions exposure, validate GLEIF LEI records, and extract real-time structured risk data to support compliance and onboarding decisions.

Instructions

Global Corporate KYB, GLEIF LEI & Sanctions Screen: Real-time structured data extraction feed for Global Corporate KYB, GLEIF LEI & Sanctions Screen.

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
maxResultsNoMaximum number of structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior1/5

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

No annotations exist, so the description carries the full behavioral burden and fails it. "Real-time" and "structured data extraction feed" are the only signals; there is no disclosure of data sources, coverage regions, freshness guarantees, licensing/auth requirements, rate limits, or what happens with no company identifier supplied — notable since the only parameter is maxResults.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short but not concise: the same eight-word resource label appears twice with a filler "Real-time structured data extraction feed for" joining them. Restructuring to a single purposeful clause would both shorten and inform.

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

Completeness2/5

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

With zero annotations, no output schema, and a tool whose only input is a result cap, the description must explain what records come back and on what entity, and it does not. An agent cannot tell whether this returns a global bulk feed or screens a named company, since no company-name parameter is documented.

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 maxResults carries its own description ("Maximum number of structured items to extract."), so the schema fully documents the single parameter. The description adds no meaning beyond it, which lands at the baseline 3 for a one-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a tautology: it names the resource ("Global Corporate KYB, GLEIF LEI & Sanctions Screen") and then defines it as a "feed for Global Corporate KYB, GLEIF LEI & Sanctions Screen" — the same string twice. The domain keywords hint at screening/LEI lookup, but no specific verb or outcome is stated, so an agent learns nothing beyond what the tool name already encodes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or alternative routing guidance of any kind. With a sibling like multichain_wallet_aml_risk_screener performing adjacent AML risk work, the definition should say which entity types (corporate vs. wallet) select this tool, but it offers nothing.

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

Deploy Server

Other Tools