Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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
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 behavioral burden. It does disclose useful traits: a single parallel call instead of N calls, the upstream source (SEC EDGAR/XBRL), and correct handling of off-calendar fiscal years (AAPL Sep, NVDA Jan). However, the text is cut off mid-sentence at "type=\"drug\" pulls FA", so the drug-side behavior is never disclosed, and nothing is said about error handling when a ticker is unresolvable or how results are ordered.

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 trigger-phrase block is front-loaded and useful for matching user phrasing, but the sentence runs long and mixes routing guidance with data-source detail in one breath. The truncation at the end leaves a dangling, non-earning fragment.

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?

With no annotations and no output schema, the description must carry the safety profile and result shape itself, and it only partially does so. The company path is adequately explained, but the drug path is incomplete and nothing is said about read-only safety, failures, or response structure for a tool whose output the agent must interpret.

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 enum/array bounds are already documented, so the baseline is 3. The description adds marginal meaning by telling the agent what type="company" actually returns (latest 10-K revenue, operating income, net income, cash, long-term debt), but the parallel drug explanation is truncated, so it does not fully earn a higher score.

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?

States a specific verb and resource ("side-by-side comparison of 2-5 companies or drugs in ONE parallel call") and explicitly distinguishes itself from the competing pattern of sequential single-entity lookups. The trigger-phrase list ("X vs Y", "head to head", "rank these companies") makes the intent recognizable from user phrasing.

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?

Gives an explicit routing rule: "ALWAYS PREFER over sequential single-pack lookups when comparing entities", plus enumerated conditions (2-5 entities, ranking, which-is-bigger questions) that select this tool. This is the when-to-use/when-to-use-something-else 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.