Skip to main content
Glama

NS Pros MCP Gateway

nist-fluid-properties__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": "nist-fluid-properties__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.7/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It does disclose the multi-register fan-out nature and mentions returning an `ambiguous` outcome and a `state_coverage` field for uncovered states, but it says nothing about permissions, rate limits, result ordering, or confidence — and the text is truncated mid-sentence, so any further behavioral notes are lost.

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 clause is well front-loaded and the identifier enumeration has real value as a scan of supported jurisdictions. However, the register list is a long run-on that ends in truncated text ("the Compan"), which is a concrete structural defect rather than mere length.

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 four-parameter, multi-register fan-out tool with no output schema, the description covers the core promise plus some response-field hints (`ambiguous`, `state_coverage`). But the truncation leaves the register coverage list incomplete, and nothing is said about result shape, ranking, or failure modes, so an agent still has gaps.

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 property descriptions are unusually rich (verbatim script handling, state-as-formation-state, country gating of the IE/US registers). The description adds register-level context that maps loosely onto `country`, but contributes no syntax or interpretation details beyond what the schema already states, 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 precisely describes what comes back: the register's own id, a Companies House number, organisasjonsnummer, SIREN, CNPJ, LEI, etc. The register list and the explicit "OFFICIAL REGISTERED ENTITY" framing let an agent distinguish this from a generic company search 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?

Provides clear when-to-use guidance: "Use this when you want the OFFICIAL REGISTERED ENTITY," which implicitly routes non-official/aggregated company data elsewhere. It contains no explicit exclusions or named alternatives among the many sibling company_register_search tools, so it stops short of full routing guidance.

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.