Skip to main content
Glama

NS Pros MCP Gateway

nvd__company_register_search

Search the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back, a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corporate number, an Estonian registry code, a CRO number, a CNPJ, a US state entity number, or an LEI. Use this when you want the OFFICIAL REGISTERED ENTITY. Registers searched: Companies House (GB), Enhetsregisteret (NO), PRH/YTJ (FI), Sirene (FR), 法人番号公表サイト (JP), RIK e-Business Register (EE), the Compan

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "Equinor ASA",
      "country": "NO"
    },
    "name": "nvd__company_register_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe company name as you have it, in its own script. Pass it VERBATIM, do not strip the legal form ("Oyj", "AS", "株式会社", "Ltd"): in Japanese the form is a PREFIX as often as a suffix and 株式会社花王 and 花王株式会社 are DIFFERENT companies, so the form is often the only evidence that separates two candidates. Diacritics, full-width characters and kana are all handled.
limitNoMaximum candidates to return, 1-50 (default 10). Does not change which registers are asked, only how many rivals come back.
stateNoOPTIONAL two-letter US state ("FL", "NY", "CO"...), with country "US" (implied when country is absent). It means the state where the company is registered or was formed, not where it is headquartered: a Delaware company headquartered in California is "DE", and passing its headquarters state asks a different question (omit `state` if you only know the headquarters). A state we hold a register for narrows the search to that register alone. A state we do not (Delaware, California) is answered from GLEIF and SEC EDGAR, with the coverage stated in `state_coverage`, and every covered register is also searched for foreign registrations of a company formed there. Omit to search every covered state register.
countryNoOPTIONAL ISO 3166-1 alpha-2 of the register you mean ("GB", "NO", "FI", "FR", "JP", "EE", "IE", "US", "BR"). Narrows the fan-out, and is frequently the difference between an answer and `ambiguous` on a short name. The Irish register and the US state registers are asked ONLY when you pass "IE" or "US". The GLEIF crosswalk is asked whatever you pass, because for several jurisdictions it is the only register we can name at all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Search' and 'get ... id back' imply a read-only lookup, and the register/ID list gives useful coverage context, but rate limits, authentication needs, result ranking, ambiguity behavior, and error modes are not disclosed.

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

Conciseness3/5

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

The description is front-loaded with the core action and use case, which is good. However, it contains a very long enumeration of identifier types and ends with a truncated register list ('the Compan'), which weakens structure and polish.

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

Completeness3/5

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

For a multi-register search tool with no output schema, the description provides the use case, covered registers, and returned identifier types. It still omits the result structure and ambiguity behavior, and the truncated register list leaves the coverage section incomplete.

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 parameter descriptions already explain name, limit, state, and country semantics in detail. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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

Purpose4/5

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

The description states a specific verb and resource: searching national business registers by company name to retrieve official registered-entity identifiers. It lists the covered jurisdictions and the kinds of IDs returned, so the task is clear, though it does not explicitly distinguish this tool from sibling company-register search tools.

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?

It gives a clear use case: 'Use this when you want the OFFICIAL REGISTERED ENTITY.' However, it does not state when not to use it, name alternatives, or explain how to choose among sibling company-register tools; additional routing guidance is left to the schema.

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.