Scored across 9 tools
Most tools are clearly distinct: status, subscription checks, pricing, signal retrieval, and connection info each target a different concern. The only mild overlap is get_oracle_info vs get_connection_info, both serving as entry points, but their content differs enough (contract/TEE details vs MCP client setup).
Tool names consistently use get_ or check_ or build_ prefixes with clear object nouns (oracle_info, subscription, telemetry, connection_info). Minor inconsistency: is_arbitrage_profitable uses a question-style prefix instead of get_/check_, but it is still readable and predictable.
Nine tools is well-scoped for an oracle server: it covers discovery, status, subscription management, pricing, signal access, and integration guidance. Each tool earns its place without redundancy.
The surface covers the full user journey: check status, check subscription, get cost, build purchase tx, and read the signal. Minor gaps: no tool to cancel or renew a subscription, and no direct on-chain balance check, but agents can work around these via the SDK template or external calls.