Skip to main content
Glama

registry-mcp — national company registries

by io.github.foretak

Statutory filing deadlines for a company

company_deadlines
Read-onlyIdempotent

Give the next occurrence of each statutory filing deadline a company faces.

country="NO" covers the Norwegian calendar (Regnskapsregisteret, Skatteetaten) for a company looked up by organisasjonsnummer (orgnr, org.nr) in Brønnøysundregistrene / Enhetsregisteret (brreg): årsregnskap, generalforsamling, skattemelding, aksjonærregisteroppgaven, mva-melding, a-melding. country="GB" covers the two Companies House obligations for a company number (CRN): the annual accounts filing and the confirmation statement (CS01).

Pass today (YYYY-MM-DD) for a reproducible answer; it defaults to the server's current UTC date. Quote due_date, not statutory_date. Each deadline's applies_because states where the date came from — quote it rather than presenting a date as unconditional fact: for Norway it names the legal form or flag and any assumption behind a computed date, and for the UK it says whether the date is Companies House's own published figure or one this tool computed from the statutory period. UK dates never roll forward off a weekend or bank holiday, so due_date equals statutory_date there; days_until goes negative for a filing Companies House still shows as overdue rather than rolling it to the next cycle. An empty deadlines list is a real answer — for Norway a bankrupt, deleted or compulsorily-liquidated entity or a branch/sub-unit, and for the UK any company whose status is not active — and notes explains why.

On error, this tool raises with the error text {"error": {"code", "message", "hint"}}. bad_request means today was not YYYY-MM-DD — fix the format and retry. Any lookup_company error code (invalid_id, not_found, unsupported_country, upstream_error, upstream_timeout) can also surface here, since this tool looks the entity up first — follow that code's hint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe company's national identifier. Norway (country='NO'): a nine-digit organisasjonsnummer (orgnr), e.g. '923609016'; spaces, dots and a 'NO...MVA' VAT suffix are accepted and normalised. United Kingdom (country='GB'): a Companies House company number (CRN), eight characters, e.g. '00445790' or 'OC303675'; a short number is zero-padded for you.
todayNoDate to compute deadlines from, YYYY-MM-DD. Defaults to the server's current UTC date — pass it explicitly for a reproducible answer. A value that is not YYYY-MM-DD is a bad_request naming the required format.
countryNoISO-3166-1 alpha-2 country code. 'NO' = Norway (Brønnøysundregistrene / Enhetsregisteret), 'GB' = United Kingdom (Companies House). 'UK' is not a country code here and is rejected. Call list_countries for the current set rather than hard-coding one.NO

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoCaveats to surface to the user, carried over from the company report: why the list is empty, an unclassified legal form, a status that suspends filing.
todayYesThe date 'next occurrence' was computed from, inclusive. Echoed back so the answer is reproducible and an agent can tell a cached answer from a fresh one.
countryYesISO-3166-1 alpha-2, upper-case.
registryYesRegistry slug, e.g. 'brreg'.
deadlinesNoOne entry per obligation kind, always the next occurrence, sorted by due_date. An empty list is a real answer, not an error — read `notes` for why.
company_idYesCanonical national identifier the deadlines were computed for.
company_nameNoRegistered name, so the caller can echo it back to a user.

Schema Changelog

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

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/open-world annotations, the description discloses substantial behavior: no weekend/bank-holiday rolling, negative days_until for overdue filings, empty deadlines as a legitimate answer with notes explaining why, and a detailed error contract including propagated lookup_company codes. This is far beyond what annotations supply.

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?

The description is long but organized into front-loaded purpose, country scope, output interpretation, and error handling. It earns its length for a complex two-country tool, though a few points repeat the schema's country and today descriptions.

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 multi-country deadline tool, it covers country-specific legal references, edge cases (bankrupt/deleted entities, inactive UK companies), reproducibility, error surface, and output caveats. An output schema exists, but the description still explains the nuanced meaning of due_date, statutory_date, days_until, and empty lists, leaving no obvious gap for an agent to call it correctly.

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 the schema already documents id normalization, today's format/default, and country meaning, so the description need not compensate. The prose mostly restates or reinforces this (e.g., bad_request for bad today) and adds output-usage guidance rather than new input-parameter semantics.

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?

Opens with a specific verb+resource: 'Give the next occurrence of each statutory filing deadline a company faces.' It then details the country-specific scope (Norway vs UK calendars) and names the registries involved, making the tool's job unambiguous and distinct from entity lookup/search siblings.

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

Usage Guidelines4/5

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

The description gives actionable context: pass today for reproducibility, quote due_date rather than statutory_date, and call list_countries for current set. It does not explicitly state when to choose this over lookup_company or search_company, though the distinct deadline purpose is clear from the opening sentence.

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