Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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

A4/5.0
Behavior4/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 behavioral traits: default fan-out across all registers when country is omitted, the CIK-vs-register-number disambiguation heuristics, and the warning that trailing security-class words match nothing in the FIGI lookup. The final SUPPORTED TYPES clause is truncated mid-sentence ("from GLEIF with p"), leaving the company spine's remaining sources undisclosed.

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 use-case quoting is front-loaded and the SUPPORTED TYPES label gives some structure, but the prose is a dense run-on that packs several heuristic rules into single sentences. The text terminates mid-word, signaling an unpolished definition, and the long example-question list takes space that could carry clearer guidance.

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 three-parameter resolver with no output schema, the description does explain what identifiers come back (CIK, ticker, company_name, LEI) and how to feed names correctly. It is nearly complete, with the main gap being the truncated supported-types section that would have described remaining company sources.

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 enum values and the country/value semantics are already documented in the input schema, and most of the description's parameter talk restates them. It does add the cross-cutting rule that a non-US country makes a bare number a national register number rather than a CIK, but that too is mirrored in the schema, so the value over structured data is marginal.

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 opens with concrete user phrasings and then states the operation in a verb+resource form: "resolve a user-spoken NAME to the canonical/official identifiers other tools require as input." It names the entity domains it covers (company/CIK/ticker/LEI, drug names) and the upstream sources (SEC EDGAR, GLEIF), so an agent can tell this apart from a facts-lookup or register-search sibling.

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?

"Use FIRST whenever you have a name but need an ID" gives an explicit ordering rule and the triggering condition, which is strong guidance. It does not explicitly name sibling alternatives such as entity_profile or company_register_search, nor state when not to use it, so it falls short of a 5.

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.