Skip to main content
Glama

NS Pros MCP Gateway

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

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose provenance (SEC EDGAR/XBRL) and a genuine gotcha — off-calendar fiscal years like AAPL Sep and NVDA Jan are handled correctly — which is useful beyond the schema. But it says nothing about the 2-5 entity cap behavior, error handling for unknown tickers, or result ordering, and the drug branch's data source is truncated away.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The opening is a dense wall of quoted trigger phrases separated by slashes, which buries the actual capability behind keyword bait. The core routing rule ("ALWAYS PREFER over sequential single-pack lookups") should have led, and the text is truncated mid-sentence, so the structure is neither front-loaded nor complete.

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 no output schema, the agent needs to know what comes back; the description lists the company metric set, which partially covers that. However, the truncation means the drug path and any return-shape details for it are absent, leaving a real gap for half the enum's surface.

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 the enum, minItems=2, maxItems=5, and per-type examples are already documented in the schema. The description reinforces that type selects the data source and that values are tickers/CIKs vs drug names, but adds little syntax or format detail the schema does not already supply, 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?

The description names a specific operation: side-by-side comparison of 2-5 companies or drugs in one parallel call, and it spells out which metrics are pulled for type="company" (revenue, operating income, net income, cash, long-term debt). It is distinguishable from single-entity lookups, though the sentence is cut off mid-word at "type=\"drug\" pulls FA", leaving the drug branch's purpose incomplete.

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?

Explicit routing guidance is given: use this over sequential single-pack lookups when comparing entities, plus a set of trigger phrasings ("X vs Y", "which is bigger"). What is missing is a named alternative for the non-comparison case; the agent is told when to use it but not the sibling to fall back to for a single entity.

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.