Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose meaningful behavior: data comes from SEC EDGAR/XBRL, figures are the LATEST 10-K revenue, operating income, net income, cash and long-term debt, and off-calendar fiscal years are handled (AAPL Sep, NVDA Jan). It omits permissions, rate limits, failure behavior when a ticker is unknown, and the drug-mode behavior 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 trigger phrases are front-loaded and useful for retrieval, but the opening is a dense keyword string rather than a clean statement of purpose, and the text terminates abruptly mid-sentence. Every phrase is on-topic, yet the truncation means the structure does not resolve into a complete definition.

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 so for company mode but not for drug mode, and it never states the shape of the comparison result (per-entity rows vs. a ranked table). For a two-parameter tool with an enum, the company side is adequately covered, but the missing half leaves an agent unable to predict drug-mode output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already labels both parameters and the enum. The description still adds real meaning beyond that by explaining what each type value actually retrieves (company = latest 10-K fundamentals from SEC EDGAR/XBRL), which the bare enum does not convey. The corresponding explanation for type="drug" is cut off, so half the enum semantics are missing.

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?

Names a concrete operation (side-by-side comparison of 2-5 companies or drugs in one call) and enumerates the entity types it covers, so the resource and scope are unmistakable. It loses a point because the sentence describing the drug mode is cut off mid-word ("pulls FA"), leaving half the purpose stated but unfinished.

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?

Gives explicit trigger phrases ("X vs Y", "which is bigger", "rank these companies") and a clear routing rule: ALWAYS PREFER this over sequential single-pack lookups when comparing entities. It stops short of a when-not condition or naming a specific sibling tool to use instead for non-comparative lookups.

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.