Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__entity_profile

"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER", full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO patents, federal contracts (USAspending), FDA-licensed biologics (Purple Book), H-1B hiring (DOL LCA),

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": "npi-registry__entity_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes"company" or "ticker", both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon.
valueYesTicker (e.g., "AAPL"), zero-padded CIK (e.g., "0000320193"), or company name (e.g., "Moderna"). A NAME now resolves through the national business registers as well as SEC EDGAR, so a non-US company returns its register identity and record rather than `resolved: false`.
countryNoOPTIONAL ISO 3166-1 alpha-2 of the business register you mean ("NO", "FI", "GB", "JP", "FR", "EE", "BR"). Only affects a NAME lookup, and is often what separates the company you mean from a US namesake. When a name resolves to a register entity with no CIK, the SEC/CIK-keyed sections are reported under `sources_skipped` with reason `not_queried`, they were never asked, which is not the same as having failed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does useful work by naming the external systems fanned out to (EDGAR, XBRL, USPTO, USAspending, Purple Book, DOL LCA), which signals breadth, latency, and partial-failure risk. It does not state whether results are cached, how long a fan-out takes, what happens when one source fails, or whether the call is read-only. The sentence is also cut off mid-list, so the disclosure of sources is incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly half the text is a run-on list of quoted user utterances joined by slashes before the actual purpose appears, so the definition is not front-loaded. The substantive portion terminates mid-sentence at "(DOL LCA),", leaving a dangling conjunction. The example queries duplicate what the schema's `examples` already demonstrate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a multi-source fan-out with no output schema and no annotations, the description should convey what a profile contains, how sources are reported, and any coverage caveats; instead it truncates while still enumerating sources and never describes the response. It also asserts "US public company" while the schema documents non-US register resolution, leaving the agent unsure which claim governs. The substantive content an agent needs before calling is therefore incomplete.

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 all three parameters carry substantive descriptions (including enum behavior for `type` and the ISO country hint for `country`), so the schema does the heavy lifting. The description adds only an implicit "$TICKER" convention through its example query and says nothing about name resolution or the country qualifier. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "full cross-source profile of a US public company in ONE parallel call" gives a specific resource (company) and an explicit scope (all sources, single call), and it names what it replaces (chaining single-pack SEC/XBRL/news lookups). It loses a point because the leading block of seven quoted user utterances buries the actual purpose statement and the "US public company" framing conflicts with the schema's claim that non-US register names resolve. Sibling differentiation is present but only against a generic class of lookups, not a named 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?

"ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view" is a direct when-to-use rule plus the alternative it beats. The example queries function as trigger phrases. It stops short of when-not guidance (e.g., a single-fact question should go to company_facts or resolve_entity), so it is clear context without exclusions.

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.