Skip to main content
Glama
Sign In

mcp-livedatapro

by site.livedatapro
OverviewDiscussionsAdmin

getCorporateDirectorsUbo

Retrieve active corporate directors, C-suite officers, ultimate beneficial owners (UBO), and disqualified officer flags. Use when identifying a company's active C-suite officers, board directors, Ultimate Beneficial Owners (UBOs with >25% equity), and PEP/sanctions screening flags for AML/KYB compliance. Do not use for basic VAT number validation (use verifyCompanyRegistryVat) or HR job openings (use getCorporateJobPostings).

Input Schema

NameRequiredDescriptionDefault
jurisdictionNo2-letter ISO country or US state registration code (e.g., GB, US-DE, DE; defaults to 'US-DE').US-DE
company_id_or_nameYesOfficial company registration number or exact registered legal entity name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / company_id_or_name / examples
      Added value: +[
+  "OpenAI OpCo LLC"
+]
    • addedInput schema / properties / company_id_or_name / minLength
      Added value: +2
    • addedInput schema / properties / jurisdiction / default
      Added value: +"US-DE"
    • addedInput schema / properties / jurisdiction / examples
      Added value: +[
+  "GB"
+]
    • addedInput schema / properties / jurisdiction / pattern
      Added value: +"^[A-Z]{2}(-[A-Z0-9]{2,3})?$"
  2. Changed2 schema fields changed
    • changedInput schema / properties / company_id_or_name / description
      Previous value: -"Company registration number or exact legal name"New value: +"Official company registration number or exact registered legal entity name."
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"2-letter country or state code (e.g., UK, US-DE, DE)"New value: +"2-letter ISO country or US state registration code (e.g., GB, US-DE, DE; defaults to 'US-DE')."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the safety/behavioral burden and does well by specifying that only active directors/officers are returned and that UBOs are those with >25% equity. It also discloses inclusion of disqualified officer and PEP/sanctions flags. It does not mention authentication, rate limits, pagination, or return format, which keeps it from a 5.

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 description is three sentences, front-loaded with the core purpose and follow-up use/exclusion guidance. Every sentence contributes to selection or scope, with no repetition or 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?

The description is fairly complete for a compliance lookup: it defines the subject matter, key output categories, and exclusions. However, because there is no output schema and no annotations, it could say more about response shape or limitations, so it is strong but not fully complete.

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 both parameters are already documented well in the input schema. The description does not add meaningful parameter-level guidance beyond schema content, such as how to disambiguate company name vs registration number or jurisdiction behavior, so it meets the baseline 3.

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 uses a specific verb, 'Retrieve', and names the exact resource set: corporate directors, C-suite officers, UBOs, disqualified officer flags, and PEP/sanctions flags. It clearly distinguishes the tool from siblings by naming verifyCompanyRegistryVat and getCorporateJobPostings as alternatives.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool for AML/KYB compliance and when not to use it, naming the correct sibling alternatives for VAT validation and HR job openings. This leaves little inference required for tool selection.

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

All mcp-livedatapro toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources