No user-submitted related servers found.
Scored across 11 tools
Most tools target distinct resources (protocols, apps, assets, names) with different query strategies. Minor overlap exists between get_protocol and get_protocol_summary, and between get_protocol_contracts and get_contract_role, but descriptions clarify their different intents.
Tool names follow a consistent verb_noun pattern (get_protocols, identify_asset, search_assets, resolve_name). Slight inconsistency in that several verbs are used (get, identify, search, resolve, reverse_resolve) but within each verb group the pattern is uniform.
11 tools is well-scoped for a read-only ecosystem registry. Each tool serves a distinct query need without redundancy or bloat.
The tool set covers the core read operations for protocols, contracts, applications, assets, and enVoi names. Minor gaps exist such as no direct 'get all assets' or 'get contract details by ID' beyond role lookup, but the domain is well served overall.