Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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 carries the full behavioral burden, and it does disclose the important trait: a single fan-out across six external data packs rather than sequential chaining, which implies cost and latency characteristics. However, it says nothing about read-only safety, failure/partial-failure handling, or response size, and the source list is cut off mid-sentence, so the disclosure is incomplete for a multi-source aggregator.

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 intent statement and the 'ALWAYS PREFER' rule are front-loaded and high-value, but seven near-duplicate example phrasings consume most of the opening and the final sentence is truncated mid-list ('H-1B hiring (DOL LCA),'), leaving an incomplete enumeration. The routing examples earn their place; the redundancy and truncation do not.

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, so the description is the only signal about what a 'profile' returns, and it stops at naming the input sources without saying what sections, format, or volume the agent should expect. The schema covers resolution edge cases and sources_skipped semantics, which partially compensates, but a broad multi-source aggregator warrants more on result shape.

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 already explains the type enum, ticker/CIK/name resolution, and the country register semantics in detail. The description adds no parameter meaning beyond its example queries (ticker, company name). 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.

Purpose4/5

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

The description states a specific resource and scope: a full cross-source profile of a company assembled in one parallel call, and enumerates the source families (SEC EDGAR, XBRL, USPTO, USAspending, Purple Book, DOL LCA). That is far more specific than the bare tool name. It loses a point for calling it a profile of a 'US public company' while the schema says non-US names now resolve through national business registers, so the stated scope is narrower than actual behavior.

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?

It gives an explicit routing rule: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view,' which tells the agent both the preferred path and the condition selecting it. It does not name the sibling tools (company_facts, company_register_search, resolve_entity) or state when a narrow single-source lookup is the better choice, so the exclusion side is implied rather than spelled out.

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.