Skip to main content
Glama

HPSILab Quant Finance

by io.github.haiyunsky

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. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
refreshNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds important details: partial success when some tools fail, full failure only if all fail, and refresh parameter behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two well-structured paragraphs with front-loaded purpose. Every sentence adds value, no waste.

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?

Given moderate complexity and existing output schema, description covers error handling and refresh. Could list aggregated tools, but output schema likely documents return fields.

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?

With 0% schema description coverage, the description compensates by explaining symbol (example NVDA) and refresh (request fresh IV Radar data). Could be more precise but adds necessary meaning.

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 description clearly states it aggregates all quant tools into one JSON analysis, deriving direction signal, score, and summary. It distinguishes from siblings like get_iv_radar which are individual tools.

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 implies use for comprehensive stock analysis but lacks explicit when-to-use vs alternatives. However, it covers behavior when underlying tools fail, providing context for reliability.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose, from individual analytics like AI prediction and IV radar to aggregation and report generation. No overlapping functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case, with verbs like get_, generate_, and analyze_. No mixing of conventions.

Tool Count5/5

9 tools is well-scoped for a quant finance server, covering diverse analytics and outputs without being excessive or sparse.

Completeness4/5

Covers major quant finance analyses and reporting. Minor gap: no raw data access tools, but the surface is comprehensive for the intended use case.

Resources