HPSILab Quant Finance

Stock Chart Generator

generate_stock_images

Generate stock-report PNG images and return their URLs.

This is intentionally separate from analyze_stock so the JSON analysis stays
fast and light. The backend reuses the same Growth Engine image generators
used by email/social publishing.

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.

Input Schema

Name	Required	Description	Default
`force`	No
`types`	No
`symbol`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 22, 2026

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"
+  }
+]

First observedJul 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds useful behavioral context: it returns URLs, reuses the Growth Engine image generators, and explains that force controls cache regeneration. Rate limits or cost implications are not mentioned, so it falls 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 description is front-loaded and uses a clear Args structure with no wasted opening. The implementation note about reusing Growth Engine generators is useful context but slightly less essential than the rest, keeping it below a 5.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The description covers all parameters and the key separation from analyze_stock, but it does not address how this relates to the similarly named get_* chart siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully documents all three parameters. It gives a symbol example, explains that force bypasses cached PNGs and defaults to True for fresh data, and lists every allowed chart type while explaining that omitting types generates all of them.

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: 'Generate stock-report PNG images and return their URLs.' It explicitly separates the tool from analyze_stock, but it does not clearly differentiate it from the get_* chart-data siblings such as get_ai_prediction or get_equity_curve.

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 description gives clear usage context by saying it is intentionally separate from analyze_stock so JSON analysis stays fast and light. It does not state exclusions or explicitly compare the tool with the individual get_* chart tools, but the primary alternative is named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HPSILab Quant Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.