Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__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": "ntsb-investigations__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

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the fan-out model (parallel queries across six named sources) and the one-call latency implication. It says nothing about rate limits, cost, partial failures, or whether results are cached, and the text is cut off mid-sentence right where further source detail would appear. Read-only nature is only implicit.

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?

Seven quoted trigger phrases occupy the opening and push the actual purpose statement into the middle of the first sentence, which weakens front-loading. The description then terminates mid-list ("H-1B hiring (DOL LCA),"), so it is both verbose at the front and incomplete at the back.

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?

There is no output schema, and for a tool that fans out across six heterogeneous sources the description gives no sense of the response shape, section-level behavior, or how skipped sources surface. It does cover source coverage thoroughly, and the schema handles input scoping and the `sources_skipped` edge case, but the truncated ending leaves the picture partially drawn.

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 for `type`, the ticker/CIK/name forms of `value`, and the ISO-3166 `country` scoping rule are already fully documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: "full cross-source profile of a US public company," and scopes it as "ONE parallel call" over SEC EDGAR, XBRL, USPTO, USAspending, Purple Book, and DOL LCA. That is enough to separate it from single-pack SEC/XBRL/news lookups. It stops short of naming specific siblings (company_facts, company_register_search, resolve_entity), so differentiation is by category rather than by 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?

Gives concrete when-to-use triggers ("company profile for Microsoft," "everything you know about $TICKER") and an explicit preference rule: "ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view." Nothing states when NOT to use it, e.g. resolving an ambiguous name first or a narrow single-source question, so the boundary is one-sided.

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.