Skip to main content
Glama

SendGrid (Unofficial)

Compare Entities

compare_entities
Read-onlyIdempotent

"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 FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so "largest" / "most" / "biggest" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8-15 sequential lookups.

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": "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. Changed1 schema field changed
    • changedInput schema / properties / values / description
      Previous value: -"For company: 2–5 tickers/CIKs (e.g., [\"AAPL\",\"MSFT\"]). For drug: 2–5 names (e.g., [\"ozempic\",\"mounjaro\"])."New value: +"For company: 2-5 tickers/CIKs (e.g., [\"AAPL\",\"MSFT\"]). For drug: 2-5 names (e.g., [\"ozempic\",\"mounjaro\"])."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and repeatability are covered. The description adds genuinely useful behavior beyond that: parallel single-call execution, upstream sources (SEC EDGAR/XBRL, FAERS, FDA approvals, trial counts), off-calendar fiscal year handling, and metric-based sorting of results. It stops short of stating limits of the underlying data (e.g., FAERS reporting lag, XBRL availability for non-US filers), so it is strong but not fully transparent.

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 definition is front-loaded: trigger phrasings and the "ALWAYS PREFER" rule come before the operational detail, so an agent can decide quickly. It is dense with useful content, though the capitalized emphasis and long slash-delimited trigger list make it slightly noisy rather than maximally economical.

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?

There is no output schema, so the description must explain return shape — and it does: paired data per entity, pipeworx:// citation URIs, and results sorted by the primary metric so superlative queries read off the top. Combined with source disclosure and entity-count bounds, an agent has everything needed to call it correctly and interpret the result.

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%, so the schema already documents both parameters including the 2-5 range and enum. The description adds real meaning by explaining what each type value yields (revenue/operating income/net income/cash/debt for company; adverse events/approvals/trials for drug) and by giving worked examples like AAPL Sep and NVDA Jan fiscal years — but that is enrichment rather than filling a documentation gap, which keeps it near baseline.

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 states a specific verb and resource ("side-by-side comparison of 2-5 companies or drugs in ONE parallel call") and makes the scope boundary explicit by naming what it replaces ("8-15 sequential lookups"). An agent can distinguish it from single-entity lookup tools without opening the schema.

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 gives concrete selection triggers ("Compare X and Y", "X vs Y", "rank these companies") plus an explicit preference rule: "ALWAYS PREFER over sequential single-pack lookups when comparing entities." The implicit exclusion is also clear — single-entity lookups remain for non-comparative queries, so when-not-to-use is derivable from the stated scope.

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.