Loading ToolBench

Reading the current corpus…

stock-snapshot-mcp MCP server · D · ToolBench

← Browse

stock-snapshot-mcp

github.com/pforpav/stock-snapshot-mcp

A minimal, educational MCP server that provides a single stock snapshot tool using the free Alpha Vantage API.

<=2025-11-25STDIO1 tools

57/100

Definition Quality73

Protocol Readiness47

Supportability36

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

Single tool with clear naming (get_stock_snapshot) and complete input schema. Description is adequate (145 chars, within 10-1024 range) but lacks actionable context for LLM selection. Schema properly declares required fields, min/max constraints, and additionalProperties=false. However, output schema is completely undocumented, LLMs cannot plan downstream operations or extract fields from the JSON response. No error handling guidance, no recovery paths, and no documentation of what fields the returned snapshot contains.

Tools (1)

get_stock_snapshotread onlyauthsource verified73/100

Return a stock snapshot from Alpha Vantage, including meta info, latest quote, basic fundamentals (if available), and recent daily OHLCV history. Educational / demo use only.

Issues (5)

HIGHtool ↗

Output schema completely undocumented. Tool returns JSON snapshot but LLMs have no visibility into field structure, types, or what data is available. Prevents downstream tool composition and forces LLMs to guess at response shape.

get_stock_snapshot

HIGHtool-description ↗

Tool description lacks WHEN/WHY context. Current description states WHAT (returns snapshot) but not WHEN to call it vs alternatives or what prerequisites exist (API key, rate limits). LLMs cannot determine if this is the right tool for a user's intent.

get_stock_snapshot

HIGHrecovery-guide ↗

No error handling guidance. Tool can fail (invalid symbol, API rate limit, missing API key) but provides no recovery hints. LLMs receive raw errors with no actionable next steps.

get_stock_snapshot

MEDIUMtool-description ↗

Parameter descriptions lack format/constraint details. 'history_days' has min/max in schema but description does not explain what happens if omitted (defaults to 60) or why the limit is 100. 'symbol' description uses examples (AAPL, MSFT, TSLA) instead of format constraints.

Recommendations

Document the output schema in the tool description or as a separate schema field. Specify: 'Returns object with keys: meta (company info), quote (latest price/volume), fundamentals (P/E, market cap, etc.), history (array of OHLCV candles). Each candle has: date, open, high, low, close, volume.'
Enhance tool description to include WHEN to use it: 'Use this to fetch current stock data for analysis, valuation, or trend assessment. Requires ALPHAVANTAGE_API_KEY environment variable. Rate-limited to 5 calls/min on free tier.'
Add error recovery guidance in description: 'If symbol is invalid, try search_stocks() first. If rate-limited, wait 60 seconds before retrying. If API key missing, set ALPHAVANTAGE_API_KEY environment variable.'
Replace example values in parameter descriptions with format constraints. Change 'e.g. AAPL, MSFT, TSLA' to 'Uppercase ticker symbol (1-5 characters, alphanumeric only).'
Document result limits and pagination: 'Returns up to history_days candles (max 100). If more history needed, call multiple times with different date ranges or use a dedicated historical data tool.'

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

First recorded score · v2 rubric

57/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	57	<=2025-11-25	v2