Skip to main content
Glama

compare_companies

Head-to-head comparison of TWO companies (mirrors the /compare/{a}-vs-{b} page): the same real, dated side-by-side metrics — price, market cap, P/E, PEG, margins, ROE/ROA, debt/equity, revenue growth, dividend yield + streak, beta, 1-year return — plus each company's one-line pitch. A metric absent for either company is returned as null (never fabricated). Both tickers must be in the covered universe: US public companies: S&P 500 + NASDAQ-100 + Dow Jones + Russell 1000 + Russell 2000 (deduped — effectively the Russell 3000 plus the Dow), spanning large-, mid-, AND small-cap companies, plus the major US exchange-traded funds (ETFs). UK public companies: the FTSE 350 (FTSE 100 + FTSE 250), listed on the London Stock Exchange. Data: SEC EDGAR filings + market-data fundamentals, each figure dated. Informational only, NOT financial advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker_a": "<ticker_a>",
      "ticker_b": "<ticker_b>"
    },
    "name": "compare_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticker_aYesFirst ticker, e.g. AAPL.
ticker_bYesSecond ticker, e.g. MSFT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description does real work: it lists the returned metrics, states that absent figures come back as null and are never fabricated, notes data provenance (SEC EDGAR plus dated market fundamentals), and adds a 'not financial advice' caveat. It does not say what happens when a ticker falls outside the covered universe — error, empty result, or otherwise — leaving the main failure mode undisclosed.

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?

Purpose is front-loaded in the first clause and the rest follows logically: output contents, null behavior, universe constraint, provenance, disclaimer. The metric inventory and the index enumeration (including the 'deduped — effectively the Russell 3000 plus the Dow' aside) are wordy but each item prevents a concrete mistake.

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

Completeness4/5

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

For a two-parameter tool with no output schema and no annotations, the description covers the main gaps itself: what comes back, how missing data is represented, and what input is legal. Only the out-of-universe failure path is missing, which is a modest gap for a read-only comparison tool.

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 per-parameter examples already carry the baseline. The description adds value beyond the schema by constraining the legal value domain — both tickers must be in the S&P 500/NDX/Dow/Russell/ETF or FTSE 350 sets — which tells the agent what inputs will actually resolve.

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 — 'Head-to-head comparison of TWO companies' — and anchors it to the /compare/{a}-vs-{b} page, which immediately separates it from the sibling profile and search tools that operate on one company.

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?

The two-company, side-by-side framing implies the right context, and it gives a hard precondition: both tickers must be in the covered universe, which is enumerated in detail by index and region. It stops short of naming an explicit alternative (e.g. get_company_profile for a single name) or an exclusion rule.

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.

Resources