Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load, and it does real work: it discloses the data source (SEC EDGAR/XBRL), that values come from the LATEST 10-K, that off-calendar fiscal years are handled (AAPL Sep, NVDA Jan), and that the call executes in parallel. What it omits is the drug-side behavior, which it began to describe before the text cuts off, plus any note on missing-data handling or permissions.

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

Conciseness4/5

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

The trigger-phrase lead is dense but functional for routing, and the substantive constraints follow in a logical order: what it is, when to prefer it, then what each type returns. It is somewhat keyword-heavy, and the trailing sentence is cut off mid-word, which hurts otherwise tight structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter comparison tool with no output schema and no annotations, the description supplies the essentials: the parallel-call behavior, the metric fields returned for companies, the fiscal-year caveat, and the routing rule against sequential lookups. The drug branch being truncated is the one real gap, but the calling contract for the tool is fully conveyed.

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, so the baseline is 3. The description adds some meaning by tying type="company" to a concrete metric set and by framing values as tickers/CIKs versus drug names, but the drug branch is truncated, so it does not meaningfully exceed what the schema already states.

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 states a specific verb and resource: side-by-side comparison of 2-5 companies or drugs in one parallel call, and enumerates the metric set pulled for type="company" (revenue, operating income, net income, cash, long-term debt). The truncated tail ('type="drug" pulls FA') leaves the drug half of the purpose half-stated, so it falls short of a clean 5.

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?

It names the exact user phrasings that should route here ('X vs Y', 'which is bigger', 'rank these companies', 'head to head') and gives an explicit directive: 'ALWAYS PREFER over sequential single-pack lookups when comparing entities.' The when-to-use condition and the alternative it replaces are both spelled out.

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.