Skip to main content
Glama

HPSILab Quant Finance

Stock Chart Generator

generate_stock_images

Generate stock-report PNG images and return their URLs, with the charts attached as PNG image content so the assistant can see them.

The JSON (symbol, status, images with url/status, disclaimer) is the same
with or without attachments; the image blocks are added after it.

Args:
    symbol: Stock symbol, e.g. "RXRX".
    force: Regenerate images instead of using cached PNGs. Defaults to True
        so manually requested images reflect the latest available data.
    types: Optional subset of chart types. Allowed values are
        "ai_prediction", "iv_radar", "option_pressure", "monte_carlo",
        and "equity_curves". Omit to generate every chart type.
    attach_images: Attach each available chart as an image. Defaults to
        True; False returns the JSON with URLs only.

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": "generate_stock_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
typesNo
symbolYesStock ticker symbol, e.g. AAPL.
attach_imagesNo

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. Changed2 schema fields changed
    • addedInput schema / properties / attach_images
      Added value: +{
      +  "default": true,
      +  "title": "Attach Images",
      +  "type": "boolean"
      +}
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "generate_stock_imagesDictOutput",
      -  "type": "object"
      -}New value: +null
  3. Changed1 schema field changed
    • changedInput schema / properties / types / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "enum": [
      +        "ai_prediction",
      +        "iv_radar",
      +        "option_pressure",
      +        "monte_carlo",
      +        "equity_curves"
      +      ],
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds genuinely new behavior: a caching layer controlled by force, the guarantee that the JSON payload is identical with or without image blocks (images appended after), and exactly what attach_images=False returns. It stops short of noting latency/cost of chart generation, which matters for an open-world image tool.

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 core action and the return shape, then a clean Args block. Some redundancy: the Args block repeats default values already present in the schema, and the enum list duplicates the schema's anyOf enum, but the framing sentences ('added after it', 'False returns the JSON with URLs only') each earn their place.

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?

With no output schema, the description usefully enumerates the returned JSON fields (symbol, status, images with url/status, disclaimer) and explains how image blocks relate to that JSON. For a 4-param, cache-backed, open-world generation tool, the only missing piece is rough timing/cost or failure behavior per image.

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 only 25% (only symbol documented in-schema), so the description must carry the load — and it does, explaining force as cache-bypass, enumerating the five allowed types plus the omit-means-all semantics, and clarifying attach_images controls whether image blocks are appended. It mostly restates schema defaults rather than adding format/syntax detail, so it falls short of a 5.

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?

Specific verb and resource: generates stock-report PNG images, returns URLs, and attaches the PNGs as image content. It also names the chart types it can produce, which implicitly relates it to the single-chart siblings (get_iv_radar, get_monte_carlo, etc.), but it never explicitly states the distinction between 'all charts at once' here vs. the individual getters.

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?

Usage is implied rather than stated: 'force defaults to True so manually requested images reflect the latest available data' hints at on-demand image requests, and 'omit to generate every chart type' explains subsetting. There is no explicit when-to-use-this vs. when-to-call-the-single-chart-tools guidance despite five overlapping siblings.

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.