Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does so well: it discloses the upstream data sources (SEC EDGAR/XBRL), the fact that off-calendar fiscal years are normalized (AAPL Sep, NVDA Jan), and that lookups run in parallel. It omits auth/rate-limit behavior and the drug-side behavior is truncated mid-sentence.

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 quoted trigger phrases are front-loaded and useful for matching, and the distinction from sequential lookups comes early. However, the keyword-stuffed lead is heavy, and the description ends mid-word ('pulls FA'), which is a real structural defect that leaves the drug case unexplained.

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 must explain what comes back; it does this well for the company path (specific financial fields, fiscal-year handling) but the drug path is severed, leaving an agent unable to know what a drug comparison returns or whether units/naming differ.

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 coverage is 100% and both parameters already carry descriptions and an enum, so the baseline is 3. The description adds some value by stating which metrics each type pulls, but the 'drug' half of that explanation is truncated and no format caveats for ticker vs CIK input are added.

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

Purpose5/5

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

The description names the exact resource and operation – a side-by-side comparison of 2-5 companies or drugs in one parallel call – and spells out the concrete payload (latest 10-K revenue, operating income, net income, cash, long-term debt from SEC EDGAR/XBRL). An agent can immediately tell this apart from a single-entity lookup 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?

It gives explicit routing guidance ('ALWAYS PREFER over sequential single-pack lookups when comparing entities') plus a rich set of natural-language triggers ('X vs Y', 'which is bigger', 'rank these companies'). It does not name a specific sibling alternative by name, and the trailing drug section is cut off, so selection guidance is strong but not exhaustive.

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.