Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose real behavior: fan-out across named registers, that the GLEIF crosswalk is always queried, that unsupported states are answered from GLEIF/SEC EDGAR with coverage reported in `state_coverage`, and that `limit` changes only the number of candidates, not the registers asked. However the register list is truncated mid-word and there is no statement about rate limits, auth, or how ambiguity results are shaped beyond the word `ambiguous`.

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 opening is well front-loaded with the key use case, but the long enumeration of identifier types partially duplicates the later register list, and the definition ends abruptly mid-word ("the Compan"), which is a real structural defect rather than compactness.

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?

For a 4-parameter tool with no annotations and no output schema, the description covers fan-out behavior, ambiguity outcomes, and the `state_coverage` field reasonably well. It loses a point because the register enumeration is truncated and the return shape is only hinted at rather than described.

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 the schema already explains verbatim-name handling, the 1-50 limit default, and the registered-vs-headquarters state distinction. The description itself adds essentially no parameter meaning beyond what the schema fields provide, so the 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 specific verb and resource ("Search the NATIONAL BUSINESS REGISTERS by company name") and enumerates exactly what comes back — register id, Companies House number, organisasjonsnummer, SIREN, CNPJ, LEI, etc. The line "Use this when you want the OFFICIAL REGISTERED ENTITY" separates it from any aggregated/derived-data source, so an agent can pick it 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 Guidelines4/5

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

Gives a clear selection condition ("when you want the OFFICIAL REGISTERED ENTITY") and the schema adds routing rules for country/state (IE and US registers asked only when passed; omit state to search every covered register). It never names an alternative tool or says when NOT to use it, and the trailing "Registers searched" sentence is cut off, so guidance is strong but not complete.

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.