Loading ToolBench

Reading the current corpus…

mcp-marketstack MCP server · D · ToolBench

← Browse

mcp-marketstack

github.com/matteoantoci/mcp-marketstack

MCP Server exposing Marketstack financial data.

2026-07-28+STDIO18 tools

52/100

Definition Quality53

Protocol Readiness50

SupportabilityNot measured-

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

18 tools with mixed quality. Tools 1-4 (market data) have complete schemas with proper enums, ranges, and descriptions (70-80 range). Tools 5-12 (reference data) lack visible descriptions and schemas in source, inferred only from file paths, capped at 50. Tools 13-18 (financial instruments) have descriptions and partial schemas but missing parameter details for several. Error handling present but generic. No tool annotations (readOnlyHint). Output schemas undocumented. Average across all tools: 58.

Tools (18)

get_bond_inforead onlyauthsource verified68/100

Get real-time government bond data for a specific country.

get_dividends_dataread onlyauthsource verified76/100

Look up information about the stock dividend for different symbols.

get_end_of_day_dataread onlyauthsource verified80/100

Obtain end-of-day data for one or multiple stock tickers.

get_etf_holdingsread onlyauthsource verified70/100

Get complete set of exchange-traded funds data based on the unique identifier code of an ETF.

get_exchange_detailsread onlyauth25/100

get_index_inforead onlyauthsource verified70/100

Get details for a specific stock market index.

get_intraday_dataread onlyauthsource verified81/100

Obtain intraday data for one or multiple stock tickers.

Issues (5)

CRITICALtool-description, constrained-input ↗

8 reference data tools (get_ticker_details, list_tickers, get_ticker_info, list_exchanges, get_exchange_details, list_exchange_tickers, list_currencies, list_timezones) have NO visible descriptions or schemas in source code. Tool definitions are inferred from file paths only, violating pattern:tool-description and pattern:constrained-input. These tools cannot be reliably selected by LLMs.

get_ticker_detailslist_tickersget_ticker_infolist_exchangesget_exchange_detailslist_exchange_tickerslist_currencieslist_timezones

CRITICALresponse-shaper ↗

Output schemas are completely undocumented. No tool declares what fields it returns, their types, or structure. LLMs cannot plan downstream calls or extract required data. Violates pattern:tool and pattern:response-shaper.

get_end_of_day_dataget_intraday_dataget_splits_dataget_dividends_datalist_indicesget_index_infolist_bonds_countriesget_bond_infolist_etf_tickers

Recommendations

Add explicit descriptions and input schemas to all 8 reference data tools (tools 5-12). Each must have a 50-200 character description explaining what it returns and when to call it.
Document output schemas for all tools. Specify field names, types (string, number, array, object), and which fields are required. Include example responses.
Add readOnlyHint: true to all tool schemas via inputSchema.properties._annotations or equivalent MCP 2026-07-28 mechanism.
Enhance error handling: categorize errors as retryable (network timeout, rate limit) vs user-fixable (invalid parameter) vs fatal (auth failure). Return actionable messages like 'Invalid country code. Try: kenya, united_states, or call list_bonds_countries() to see all options.'
Add parameter format constraints to tools 13-18. E.g., get_bond_info country param: 'Specify country name in lowercase (e.g., kenya, united_states) or call list_bonds_countries() first to discover valid values.'

Score history

Overall score trend

First recorded score · v2 rubric

52/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	52	2026-07-28+	v2