Skip to main content
Glama

compare_stocks

[Personal research only] Side-by-side comparison of 2-6 stocks as one table: TTM revenue and growth, pretax margin, net income growth and diluted EPS growth from SEC filings (each row's window ends on its ttm_to), net debt for standard layouts, delayed price, day change, distance from the 52-week high and trend, market cap, and P/E on filed diluted EPS LTM (FY + YTD - prior YTD). order lists each filed figure highest first, P/E lowest first. comparability says what revenue means per layout; cell_notes say what moves a figure. Filings are cited by accession in sources.edgar: open https://www.sec.gov/Archives/edgar/data/{cik}/{accession without dashes}/. Costs 5 credits for each ticker that returns an analysis: 10 for 2 tickers, 30 for 6. A ticker that is not covered or fails is free.

Personal research only: on every plan, this tool's output is for your own personal, non-commercial research. Do not use it in a commercial product, client deliverable or service.

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": {
      "symbols": "<symbols>"
    },
    "name": "compare_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYes2 to 6 tickers, e.g. ['NVDA', 'AMD']

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are provided, so the description carries the behavioral burden, and it discloses a lot: credit costs per returning ticker, that failed or uncovered tickers are free, delayed price usage, SEC accession citation format, output ordering rules, comparability notes, and personal-use restrictions. It does not explicitly state read-only/no-side-effect behavior or authentication needs, which keeps it short of a 5.

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 core purpose and key metrics are front-loaded, and most of the dense detail is justified by the tool's complexity. The repeated personal-research restriction and lengthy metric enumeration slightly reduce conciseness, but the structure remains readable.

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?

Given a complex comparison tool with a simple input schema and an output schema, the description covers metrics, calculation nuances, ordering, comparability, citations, cost behavior, coverage failures, and legal restrictions. An agent has enough information to invoke it correctly and interpret the main output semantics.

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?

There is only one parameter, symbols, and the schema description coverage is 100% with an example. The description restates that 2-6 stocks are compared, but adds no syntax or format meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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: a side-by-side comparison of 2-6 stocks as one table, with an explicit list of metrics. It is clear what the tool does, but it does not name or distinguish itself from similar siblings such as peer_table or analyze_stock.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for use (comparing 2-6 tickers side by side) and useful constraints around coverage and cost. However, it does not explicitly say when to use this instead of alternatives like peer_table, analyze_stock, financials, or snapshot.

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