Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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 burden. It does disclose useful behavior: a fan-out across SEC EDGAR, XBRL, USPTO, USAspending, Purple Book and DOL LCA, plus the latency implication of 'ONE parallel call'. But it discloses nothing about cost, rate limits, failure or partial-result behavior; it ends mid-sentence at 'H-1B hiring (DOL LCA),' so the source enumeration itself 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.

Conciseness3/5

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

It is front-loaded with routing examples, which is good, but it compresses everything into one long run-on sentence with seven near-duplicate phrasings of the same question. The final sentence is truncated mid-list, which hurts structure and leaves the sentence doing no work.

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 aggregation tool with no output schema, the agent needs to know what gets returned and what is left out. The description covers the source fan-out, but the truncated source list and the absent return-shape or partial-failure notes leave it only adequate.

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 schema already explains type, value and country in detail, including that 'company' and 'ticker' behave identically and what country does for name resolution. The description adds only the observation that a ticker symbol like $TICKER is a valid input, which does not exceed the schema. Baseline 3 applies when the schema does the work.

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 names a specific deliverable ('full cross-source profile') and a specific resource, and backs it with example user utterances ('research Acme', 'everything you know about $TICKER') that make the intent unambiguous to an agent. The one flaw is that it frames the scope as 'a US public company' while the schema explicitly says a non-US name resolves through national business registers, so an agent reading only the description could wrongly exclude non-US entities.

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 selection rule: 'ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view.' That is a real when-to-use statement with a named alternative class. It does not say when *not* to use it (for example, when one source pack fully answers the question), so the guidance is directional rather than complete.

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.