Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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.7/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 behavioral burden. It does disclose genuinely useful behavior — cross-source identity spine composition, ambiguity handling for bare numbers, and that omitting country fans out across every known register — but the text is truncated mid-sentence ('with p'), so the disclosure of the drug and lei types and any downstream behavior is cut off. Return shape and not-found behavior are not described despite no output schema existing.

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 quoted user-phrase preamble is front-loaded and aids retrieval, but it is long and only loosely structured, and the SUPPORTED TYPES block is cut off mid-word ('with p'), leaving a visibly broken definition. The core instruction is buried after six example phrases.

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 no output schema and no annotations, the description should fully explain supported entity types and what is returned. It starts that explanation but truncates, so the 'drug' and 'lei' types and the returned field set are only partially covered, leaving the agent to infer from the schema alone.

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 itself already documents type, value, and country in exceptional detail, including the bare-number disambiguation rules. The description adds the supported-type overview but is truncated before covering drug/lei semantics, so it adds little beyond the schema. Baseline 3 is appropriate.

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+resource ('resolve a user-spoken NAME to the canonical/official identifiers other tools require as input') and anchors it with concrete user phrasings (ticker, CIK, LEI, RxCUI, 'who owns X'). An agent can immediately tell this is a name-to-identifier resolution tool rather than a data-fetch tool.

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 sequencing guidance is given: 'Use FIRST whenever you have a name but need an ID,' which tells the agent this precedes downstream identifier-consuming tools. The country parameter description further explains when to narrow vs. omit. It stops short of naming sibling resolvers or stating when not to use it.

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.