Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__resolve_entity

"What's the ticker for..." / "find the CIK for..." / "what's the LEI for..." / "what's the RxCUI for..." / "look up the ID for..." / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y", resolve a user-spoken NAME to the canonical/official identifiers other tools require as input. Use FIRST whenever you have a name but need an ID. SUPPORTED TYPES: "company" (cross-source identity spine: 10-digit CIK + ticker + company_name from SEC EDGAR, legal-entity LEI from GLEIF with p

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": {
      "type": "company",
      "value": "AAPL"
    },
    "name": "ntsb-investigations__resolve_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesEntity type: "company", "drug" or "lei" (a 20-character LEI; "company" also recognises an LEI by its check digits).
valueYesFor company: ticker (AAPL), CIK (0000320193 or 320193), LEI (HWUPKR0MPOU8FGXBT394), or name. A bare number is read as an SEC CIK only as 320193 or 0000320193; with a non-US `country`, or with 8-9 digits starting with 0 (a Companies House number), it is not a CIK and is not asserted as one. A bare number of 7 digits or fewer sent without `country` is always read as an SEC CIK, so a short register number (for example an Irish CRO or a US state filing number) that equals a real CIK will resolve to that SEC filer; send a non-US `country` with a foreign register number. A US state filing number cannot be resolved by number; search by company name instead. For drug: brand or generic name (e.g., "ozempic", "metformin"). Pass the ENTITY NAME ONLY, for a bond that is the ISSUER exactly as printed ("NEW YORK ST DORM AUTH"), never the question's full noun phrase ("NEW YORK ST DORM AUTH revenue bonds"): the FIGI lookup matches instrument names, so trailing security-class words match nothing.
countryNoOPTIONAL ISO 3166-1 alpha-2 of the country whose business register you mean ("NO", "FI", "JP", "GB", "FR", "EE", "BR"). Narrows the national-register fan-out and is often the difference between the right company and a US namesake, "Apple" with country "NO" is a Norwegian company, not Apple Inc. Omitting it searches every register we can name, which is the right default when you do not know. A bare number with a non-US country is that country's register number, never read as an SEC CIK (a 10-digit number still is). company only; ignored for drug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses the national-register fan-out default, the SEC CIK vs. foreign register-number ambiguity, the 8-9 digit Companies House case, and the FIGI instrument-name matching risk. These are real behavioral footguns an agent would otherwise trip over. It falls short of a 5 because it never describes the shape of the result (no output schema exists) and says nothing about limits or failure modes.

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 purpose statement is buried behind a long run of quoted trigger phrases, pushing the most important sentence back. Worse, the text is truncated mid-sentence ('legal-entity LEI from GLEIF with p'), so a chunk of the SUPPORTED TYPES content is lost, and the remaining text duplicates the schema rather than extending it.

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 3-parameter tool with complete schema coverage, the parameter side is adequately covered, but the description is cut off before finishing the entity-type list it advertises, and with no output schema the agent gets no sense of what a resolved payload contains (a single ID? a ranked set of candidates? what happens on ambiguity?). The truncation makes it materially incomplete for a resolution tool where disambiguation output shape matters.

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 parameter meanings are already fully documented in structured data; the description largely restates them (the type enumeration and country rules appear verbatim in both places). The one genuinely additive hint, 'Pass the ENTITY NAME ONLY... never the question's full noun phrase', also appears in the schema. Baseline 3 applies when the schema does the heavy lifting.

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 states a precise verb and resource: 'resolve a user-spoken NAME to the canonical/official identifiers other tools require as input', and enumerates supported entity types (company/drug/lei) with the identifiers returned (CIK, ticker, LEI, RxCUI). The leading example phrasings ('what's the ticker for...', 'who owns X') map directly onto the tool's job, so an agent can match intent to tool instantly.

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?

Explicit placement guidance: 'Use FIRST whenever you have a name but need an ID', which tells the agent this is a prerequisite step before other ID-consuming tools. It also gives the when-to-omit rule for `country` ('the right default when you do not know'). It lacks explicit when-not-to-use guidance and never names a sibling alternative, but the context is still clear.

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.