Skip to main content
Glama

Stock Expert AI Research

Stock Expert AI: stock summary (MoonshotScore)

stockexpertai_get_stock_summary
Read-onlyIdempotent

Get Stock Expert AI's research summary for one US-listed stock: MoonshotScore (0-100, educational rating), band (Exceptional / Strong / Fair / Weak), grade, which scoring engine produced it, the five pillar scores (0-100, sector-relative), the engine's one-line read, one-sentence bull and bear case, score and analysis dates, next provider-listed earnings date and the canonical page URL. Price, market cap and P/E are not returned: full figures on the page (canonicalUrl).

Use when: a user asks "what does Stock Expert AI say about NVDA", "NVDA MoonshotScore", "is NVDA a good stock right now" (answer with the rating and both cases; never as a recommendation), "NVDA bull vs bear case". Don't use when: you need a side-by-side of several tickers (use stockexpertai_compare_stocks) or a ranked list (use stockexpertai_screen_stocks).

Args: ticker (string) — US ticker symbol. Returns (structuredContent): { ticker, company, exchange, sector, industry, moonshotScore|null, grade, band, scoreEngine, scoreAsOf, pillars: [{ pillar, score, state }], strongestPillar, weakestPillar, scoreRead, bullCase, bearCase, analysisDate, nextEarningsDate, figuresAsOf, canonicalUrl, fullFigures, disclaimer }. Errors: "No summary for " when the ticker is unknown or its page is too thin to publish — try stockexpertai_search_ticker with the company name. Funds/ETFs/warrants/SPACs carry no MoonshotScore (moonshotScore = null). 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": {
      "ticker": "<ticker>"
    },
    "name": "stockexpertai_get_stock_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesUS ticker symbol, e.g. NVDA, BRK.B, AAPL (case-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value beyond that: it states what is NOT returned (price, market cap, P/E) and where to get it, documents the "No summary for <ticker>" error with a recovery step, and explains that funds/ETFs/warrants/SPACs return moonshotScore = null. The remaining gap is return-format behavior for a no-output-schema tool, though the Returns block substantially covers 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?

Strongly front-loaded and cleanly sectioned (purpose, Use when, Don't use when, Args, Returns, Errors, caveats), so an agent can scan to the needed part. Minor waste: the "price, market cap and P/E are not returned" point appears in the opening sentence and again under "Derived output only", and the not-advice disclaimer is stated 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, so the description must describe the return payload — and it does, field by field, including nullable moonshotScore and the nested pillars shape. Combined with the error handling, ETF caveat and the financial-advice framing, an agent has everything needed to call and interpret this tool correctly.

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% and the single ticker parameter is already documented with examples and case-insensitivity in the schema. The description's "Args: ticker (string) — US ticker symbol" restates rather than adds. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 opening sentence names a specific verb ("Get") and resource ("research summary for one US-listed stock") and enumerates the exact payload — MoonshotScore, band, grade, pillars, bull/bear case, dates, canonical URL. It also explicitly scopes to single-ticker lookups, which separates it from compare_stocks and screen_stocks without opening their schemas.

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?

There is an explicit "Use when" block with four realistic user phrasings, including the tricky "is NVDA a good stock right now" case with an instruction on how to answer (rating plus both cases, never a recommendation). The "Don't use when" block names the two concrete alternatives and the condition that selects each, leaving nothing to inference.

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