Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__compare_entities

"Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head", side-by-side comparison of 2-5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + operating income + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly, AAPL Sep, NVDA Jan, etc.). type="drug" pulls FA

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",
      "values": [
        "AAPL",
        "MSFT"
      ]
    },
    "name": "npi-registry__compare_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesEntity type: "company" or "drug".
valuesYesFor company: 2-5 tickers/CIKs (e.g., ["AAPL","MSFT"]). For drug: 2-5 names (e.g., ["ozempic","mounjaro"]).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 burden. It discloses useful behavior: one parallel call instead of sequential lookups, LATEST 10-K as the data vintage, and correct handling of off-calendar fiscal years (AAPL Sep, NVDA Jan) — genuinely valuable context. It says nothing about failure modes (unknown ticker, ambiguous drug name), result ordering, or partial-failure behavior, and the drug-data disclosure is truncated.

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 query-phrase opener is front-loaded and useful for matching, and the prefer-over-alternative directive comes early. However, the pseudo-code phrasing list is dense, and the text terminates mid-sentence ("pulls FA"), which is a structural defect rather than concision.

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 2-parameter tool with a fully documented schema and no output schema, most essentials are present: entity types, count limits, and what the company path returns. The truncation leaves the drug path and any result-shape expectations undefined, which is a real gap for an agent deciding between the two modes.

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 both parameters are already documented in the schema, and the enum values are self-explanatory. The description adds some meaning by explaining what each type value actually retrieves for the company branch, but the equivalent explanation for the drug branch is cut off, so the added value is partial.

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 action and resource: side-by-side comparison of 2-5 companies or drugs in a single call, with named data sources (SEC EDGAR/XBRL 10-K revenue, operating income, net income, cash, long-term debt). The scope and the company branch are unambiguous. It falls short of 5 only because the drug branch is cut off mid-word ("type=\"drug\" pulls FA"), leaving half the tool's coverage unspecified.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states "ALWAYS PREFER over sequential single-pack lookups when comparing entities," naming the alternative pattern to avoid and the condition that triggers this tool. It also maps colloquial user phrasings ("X vs Y", "which is bigger", "rank these companies") to the tool, which is exactly the routing guidance an agent needs.

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.