Skip to main content
Glama

HPSILab Quant Finance

Stock Analysis

analyze_stock
Read-onlyIdempotent

Aggregate all quant tools into one JSON stock analysis.

The tool reuses the existing MCP tools as its data sources, then derives a
direction signal, direction score, bullish factors, bearish factors and
plain-English summary. `tool_responses` carries each source's full text
(AI prediction, IV radar, option pressure, equity curve, Monte Carlo with
its distribution), including their data dates; `confidence_score_meaning`
explains the 0-100 score. If one underlying tool is gated, unavailable or
raises an error, the remaining tools still contribute to the final result
(status "partial"); if every underlying tool fails, the whole call fails
(status "error", isError=True) instead of a misleadingly "successful"
empty analysis.

Args:
    symbol: Stock symbol, e.g. "NVDA".
    refresh: Request fresh IV Radar data instead of using the backend's
        fresh IV cache. Defaults to False.
    lang: Language for `summary`, `bullish_factors` and `bearish_factors`
        - "en" (default), "zh" or "ja"; regional forms like "zh-CN" are
        accepted. Everything else in the response, `signal` included, is
        language-independent, so an existing caller that omits this gets
        byte-identical output to before.

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": {
      "symbol": "<symbol>"
    },
    "name": "analyze_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
symbolYesStock ticker symbol, e.g. AAPL.
refreshNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / symbol / description
      Added value: +"Stock ticker symbol, e.g. AAPL."
    • addedInput schema / properties / symbol / examples
      Added value: +[
      +  "AAPL"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "default": "en",
      +  "title": "Lang",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the degradation contract: partial results when one source fails, a hard `error`/isError=True when all sources fail rather than a misleading empty success, and that `tool_responses` carries each source's full text with its data dates. That is behavior an agent could not infer from schema or annotations.

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-loaded with the one-line purpose, then a behavior paragraph, then a clean Args block. The closing clause about byte-identical output for callers omitting `lang` is compatibility trivia that is slightly longer than it needs to be, but everything else earns its place.

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?

The tool is a complex multi-source aggregator, and the description covers the inputs, the failure semantics, what `tool_responses` contains, and how to read the 0-100 confidence score. With an output schema present, no further return-value explanation is required.

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 only 33% (only `symbol` is documented), so the description must compensate, and it does explain `refresh` as bypassing the backend IV cache and `lang` as affecting only summary/factors with regional forms accepted. However it leaves `symbol` format to the schema example and gives no constraints on cache-freshness tradeoffs, so the compensation is real but not complete.

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 and resource ('Aggregate all quant tools into one JSON stock analysis') and makes the aggregator role unmistakable against siblings such as get_ai_prediction or get_monte_carlo, which each supply one data source. It also enumerates the derived outputs (direction signal, score, bullish/bearish factors, summary).

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?

It states the tool reuses the existing MCP tools as data sources, which implicitly tells an agent to call this instead of chaining the individual tools, and `refresh` is scoped to IV Radar. It never says explicitly when to prefer this over calling the underlying tools directly, or that results are only as fresh as the underlying cache, so selection guidance is clear but not exhaustive.

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.