Skip to main content
Glama

registry-mcp — national company registries

by io.github.foretak

List supported national company registries

list_countries
Read-onlyIdempotent

List every national company registry this service can answer for right now, plus each one's identifier scheme (id_scheme, id_example, id_description), source URL, licence, and whether the upstream register needs a credential (requires_api_key, and api_key_env naming the environment variable that must be set for it).

Call this before your first lookup in a country you have not used here before, or whenever a user names a country you are unsure is supported — never hard-code a country list of your own, since it grows as registry modules are added with no change to any other tool's shape. Stub/example modules are hidden; only registries that actually answer are listed. This tool has no error mode; a failure here is a bug, not something to retry differently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countriesNoOne row per registry that can answer right now, sorted by country code.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description discloses hidden stub modules, the live-only nature of results, credential-related fields, and the absence of an error mode. This gives the agent important behavioral expectations not encoded in annotations.

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 dense but every sentence earns its place: scope, output fields, usage timing, anti-hard-coding guidance, hidden-module behavior, and error semantics. It is front-loaded with the core purpose and does not waste words.

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?

For a zero-input, read-only listing tool, the description covers output fields, supported-registry behavior, credentials, and failure semantics. An output schema exists for return values, and the description adds the contextual information needed for correct invocation and interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and the baseline for zero-parameter schemas is 4. The description appropriately focuses on output semantics instead, explaining exactly what fields will be returned and what they mean.

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 and resource: 'List every national company registry this service can answer for right now'. It clearly distinguishes itself from lookup/search/validation siblings by focusing on enumeration of supported registries rather than querying a company.

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?

Explicit when-to-use guidance is provided: call before the first lookup in an unfamiliar country, or whenever the user names a country the agent is unsure about. It also warns not to hard-code a country list, giving a clear boundary that prevents misuse.

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

All registry-mcp — national company registries toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation3/5

There are two pairs of conceptually overlapping tools: lookup_company vs validate_company_id (both take a country code and identifier, and validate_company_id explicitly positions itself as a 'pre-check' or 'cheap' version of lookup_company), and search vs search_company vs fetch vs company_deadlines (the connector aliases duplicate the canonical tools). The descriptions do disambiguate them, but an agent could reasonably confuse validate_company_id with a lightweight lookup rather than a pure format check, and the alias pair search/fetch adds unnecessary ambiguity.

Naming Consistency4/5

Most tools follow a clear verb_noun pattern: list_countries, lookup_company, search_company, validate_company_id, company_deadlines. However, company_deadlines breaks the pattern by putting the noun first without a verb, and fetch/search are generic aliases that do not match the family's naming convention. The core set is consistent, but the deviations are noticeable.

Tool Count4/5

Seven tools is within the ideal range for a domain-specific registry server. The main tools (list_countries, search_company, lookup_company, company_deadlines, validate_company_id) each earn their place. The two connector aliases (search, fetch) are somewhat redundant for non-ChatGPT clients, which slightly pads the count without adding real functionality, but the scope is still reasonable.

Completeness5/5

The tool surface covers the full lifecycle of a company-registry interaction: discover supported countries (list_countries), validate an identifier offline (validate_company_id), search by name (search_company), fetch full company data (lookup_company), and retrieve statutory deadlines (company_deadlines). There are no obvious dead ends: search returns ids that feed lookup_company, and lookup_company complements deadlines. For the stated purpose—answering company identity and filing-deadline questions from national registries—the coverage is complete.

Resources