Skip to main content
Glama

Company profile from Wikidata and LEI records

company_profile
Read-only

Company card for a domain or name. From Wikidata: QID, label, description, websites, inception, industries, headquarters, country, latest employee count, parent organizations, stock listings and tickers, founders (names only), legal form, LEI. From GLEIF when an LEI is known or a legal name matches exactly: legal name, jurisdiction, entity and registration status, legal and HQ city/country, parents. With match method and confidence. Sources: Wikidata, GLEIF (CC0). Price: $0.01 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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": "company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCompany name, 2 to 100 characters, e.g. Novartis AG. Matched against Wikidata labels and aliases (organizations only) and GLEIF exact legal names.
domainNoCompany website domain or URL, e.g. novartis.com. Matched against Wikidata official website statements. Either domain or name is required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the billing model ($0.01 per successful call, USDC via x402 v2, failed and no-match calls free), the upstream sources and their licensing (Wikidata, GLEIF CC0), that founders are returned as names only, and that results carry a match method and confidence.

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?

Front-loaded with the one-line purpose, followed by two source-scoped field lists and a pricing sentence; there is no filler, though the long comma-separated field enumeration is dense and could be scannable if grouped.

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

Completeness5/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 carries the return-value burden itself by enumerating returned fields, and it additionally covers cost behavior for failed/no-match calls and match-confidence metadata. For a two-parameter read-only lookup, nothing an agent needs to call it correctly is missing.

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 coverage is 100%, and the schema already explains that name is matched against Wikidata labels/aliases and GLEIF legal names while domain is matched against official website statements, so the description's 'domain or name' phrasing adds essentially nothing new. Baseline 3 applies.

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?

States a concrete resource ('Company card for a domain or name') and then enumerates exactly which fields come from Wikidata and which from GLEIF, so an agent can tell this apart from domain_whois or domain_report without opening the schema.

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?

Usage is only implied: you supply a domain or name and get a company card. The one conditional clause ('From GLEIF when an LEI is known or a legal name matches exactly') describes enrichment logic, not when to choose this tool over a sibling, and there is no guidance on choosing name versus domain input.

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