Skip to main content
Glama

Stock Expert AI Research

Stock Expert AI: compare stocks side by side

stockexpertai_compare_stocks
Read-onlyIdempotent

Compare 2-4 US stocks on Stock Expert AI's own metrics: MoonshotScore, Council Score, band, the five pillar scores (business quality, financial safety, valuation, growth durability, momentum; 0-100, sector-relative), sector, industry — plus a rule-based verdict sentence that states which ticker leads on how many metrics (it rates, it never recommends). Price, market cap and P/E are not returned: full figures on the comparison page (canonicalUrl).

Use when: "CRM vs NOW", "AMD or NVDA, which scores higher", "compare AAPL MSFT GOOGL". Args: tickers (array of 2-4 strings). Returns (structuredContent): { asOf, verdict, metrics: [{ metric, values: {TICKER: value}, leader }], summaries: [same fields as stockexpertai_get_stock_summary], missing, canonicalUrl, fullFigures, disclaimer }. Errors: fewer than two tickers resolved → lists which ones were unknown. Derived output only: Stock Expert AI's own ratings, sentences and dates. Raw market figures (price, market cap, P/E, EPS, revenue) are not returned — full figures on the page (canonicalUrl). MoonshotScore is Stock Expert AI's educational research rating, not a buy or sell recommendation. Not financial advice. Not a registered investment adviser.

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": {
      "tickers": "<tickers>"
    },
    "name": "stockexpertai_compare_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersYesTwo to four US ticker symbols

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world; the description adds real value on top: derived-output-only constraint, the fact that raw market figures are withheld and pushed to canonicalUrl, the partial-failure behavior (fewer than two tickers resolved lists the unknowns), and the ratings-not-advice disclaimer. This is behavior beyond structured data, not a restatement of it.

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?

Front-loads the metric list and the Use-when triggers, which is the right ordering. It loses a point for redundancy: the price/market cap/P/E exclusion is stated in the opening paragraph and then restated in the "Derived output only" paragraph, and the not-financial-advice point appears twice.

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?

No output schema exists, but the description enumerates the structuredContent shape (asOf, verdict, metrics with leader per metric, summaries, missing, canonicalUrl, fullFigures, disclaimer) plus the error path. For a one-parameter comparison tool that is more than enough for an agent to call it 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 coverage is 100% and there is a single parameter, so the schema already documents the type, min/max items and format. The description echoes it as "tickers (array of 2-4 strings)" and adds nothing about symbol normalization, case handling, or duplicate input behavior. Baseline 3 is appropriate.

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 (compare) plus the exact resource and scope: 2-4 US stocks on named proprietary metrics (MoonshotScore, Council Score, five pillar scores, sector/industry) with a verdict sentence. It also explicitly bounds what the tool will not produce (price, market cap, P/E), so an agent can distinguish it from a single-ticker summary or a screener 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 Guidelines4/5

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

The "Use when" block gives three concrete trigger phrasings ("CRM vs NOW", "AMD or NVDA, which scores higher", "compare AAPL MSFT GOOGL") that map cleanly to the tickers array. It stops short of explicitly naming alternatives such as the single-stock summary or screener and saying when those are preferred, so the routing logic is strong but not fully closed.

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