Loading ToolBench

Reading the current corpus…

mcp-workshop MCP server · D · ToolBench

mcp-workshop

Model Context Protocol server providing stock market data functionality using Yahoo Finance API with CSV fallback support. Offers tools for retrieving current stock prices and comparing multiple stock symbols across three implementation variants (raw, mcp, course).

<=2025-11-25STDIO2 tools

58/100

Definition Quality73

Protocol Readiness47

Supportability39

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

Two tools with clear verb-noun naming (get_stock_price, compare_stocks) and reasonable descriptions (120-180 chars). Input schemas present with type definitions and parameter descriptions. However, output schemas are undocumented (tools return plain strings, not structured objects), and error handling lacks recovery guidance. No tool annotations (readOnlyHint, idempotentHint). Parameters are minimal but well-described. Missing pagination, result limits, and structured response formats expected in production tools.

Tools (2)

compare_stocksread onlysource verified73/100

Compare the current stock prices of two ticker symbols. First tries Yahoo Finance API, then falls back to local CSV file for each symbol.

get_stock_priceread onlysource verified73/100

Retrieve the current stock price for the given ticker symbol. First tries Yahoo Finance API, then falls back to local CSV file.

Issues (5)

HIGHresponse-shaper ↗

Output schemas undocumented. Tools return plain strings instead of structured objects with typed fields. LLMs cannot extract data for downstream tool calls or plan multi-step workflows.

get_stock_pricecompare_stocks

HIGHtool-annotations ↗

No tool annotations. Tools lack readOnlyHint, idempotentHint, or destructiveHint. LLMs cannot determine if tools are safe to retry or have side effects.

get_stock_pricecompare_stocks

MEDIUMrecovery-guide ↗

Error handling lacks recovery guidance. Errors return plain text (e.g., 'Could not retrieve price...') without actionable next steps or available alternatives.

get_stock_pricecompare_stocks

MEDIUMpaginated-result ↗

No result limits or pagination. Tools accept single symbols but lack batch variants. Comparing many stocks requires sequential calls, wasting tokens and latency.

compare_stocks

Recommendations

Return structured JSON objects instead of plain strings. E.g., {"symbol": "AAPL", "price": 150.25, "source": "yfinance", "timestamp": "2024-01-15T14:30:00Z"} enables downstream tool chaining and data extraction.
Add tool annotations: mark both tools with readOnlyHint=true and idempotentHint=true so LLMs know they are safe to retry without side effects.
Enhance error messages with recovery guidance. E.g., 'Symbol INVALID not found. Valid symbols in local data: AAPL, MSFT, GOOGL. Try search_symbols() for more options.'
Add a batch_compare_stocks(symbols: list[str]) tool to enable efficient multi-stock comparisons in a single call, reducing token waste and latency.
Document data source and freshness in responses. Include 'last_updated' timestamp and 'source' field so agents can reason about data quality and decide whether to refresh.

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

58/100

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