Related Servers

Each tool has a clearly distinct purpose with no overlap: get_contract_role focuses on contract roles, get_protocol and get_protocol_summary provide different levels of protocol detail, get_protocol_contracts lists contracts, get_protocols lists protocols, identify_application and identify_asset handle different resource types, and the name tools (resolve_name, reverse_resolve_address, search_names) are clearly scoped to static registry operations. An agent can easily distinguish between them based on their specific targets.

All tools follow a consistent verb_noun pattern with snake_case, using verbs like 'get', 'identify', 'resolve', 'reverse_resolve', and 'search' paired with specific nouns (e.g., contract_role, protocol, protocols, application, asset, name, address). This predictability makes it easy for an agent to understand the action and target from the name alone.

With 10 tools, the count is well-scoped for the domain of Voi ecosystem information and static name registry operations. Each tool serves a unique function, covering protocol discovery, contract details, asset/application identification, and name resolution without redundancy, making the set efficient and focused.

The tool set provides comprehensive coverage for querying Voi protocols, contracts, assets, applications, and static name registry data, with clear CRUD-like operations (e.g., get, list, identify, resolve). A minor gap exists as the server defers live name resolution to another MCP server (UluCoreMCP), but this is explicitly noted and does not hinder core functionality, allowing agents to work around it.