No user-submitted related servers found.
Scored across 5 tools
Each tool has a fairly distinct purpose: web_search vs web_fetch (find vs retrieve), market_search vs market_invoke (discover vs execute), and metis_verify is a standalone verification endpoint. The only slight overlap is that market_invoke can run arbitrary hub capabilities while metis_verify runs a specific one, which could raise 'which do I call?' questions, but the descriptions clarify the difference.
All five tools follow the same {domain}_{verb}_tool snake_case convention (web_search_tool, market_invoke_tool, market_search_tool, metis_verify_tool, web_fetch_tool). The redundant '_tool' suffix is unnecessary but applied uniformly, so it remains fully predictable.
Five tools is a lean but reasonable set covering search, fetch, market discovery, invocation, and verification. It is on the thin side for a market/hub server since no tool exposes trial quota, hub config, or errors-as-state beyond what invoke returns, but nothing feels padded.
The core loop is covered: discover capabilities (market_search), run one (market_invoke), verify output (metis_verify), plus web search/fetch for grounding. Minor gaps exist (no tool to inspect remaining trial invokes or hub status), and paid escrow is intentionally excluded, but agents can work around these.