Compatibility alias for onchain_lookup address balances. Prefer onchain_lookup for new clients.
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | EVM address (0x...) | |
| chainId | No | 43114 for C-Chain mainnet, 43113 for Fuji | 43114 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden of behavioral disclosure. It offers only the alias/deprecation context and 'address balances,' but no details on safety, permissions, rate limits, or operational side effects. This is minimal for a tool with zero annotation support.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, no wasted words. The first sentence states the tool's nature, and the second provides actionable directional advice. Perfectly front-loaded and concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple compatibility alias with full schema coverage, the description effectively communicates purpose and replacement. It doesn't explain return formats, but the explicit pointer to onchain_lookup and the absence of an output schema mitigate this gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both address and chainId already described. The description adds no parameter-specific information beyond referencing balances, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the tool as a compatibility alias for onchain_lookup address balances, clearly indicating it retrieves balances. It distinguishes from siblings by pointing to the preferred onchain_lookup tool, though the exact verb 'get' is implied rather than explicitly stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states 'Prefer onchain_lookup for new clients,' giving clear when-to-use guidance and naming the alternative tool. This leaves no ambiguity about the intended usage and deprecation status.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools are redundant due to compatibility aliases (avalanche_docs_* vs docs_*, blockchain_get_* vs onchain_lookup) and overlapping functionality (chain_stats vs onchain_query, onchain_activity vs onchain_query ops, acp_list vs info_acps). Agents may struggle to select the correct tool when multiple appear to serve the same purpose, despite descriptions clarifying aliases.
Naming patterns are inconsistent: some tools use noun_verb (acp_list, docs_fetch), some use verb_noun (build_plan), and others use prefixes like platform_get_, info_get_, and onchain_. The mix of styles (snake_case, noun phrases, verb phrases) makes it hard to predict tool names.
With 48 tools, the count is high and inflated by compatibility aliases and granular platform_get_* wrappers. The scope spans multiple domains (docs, on-chain, platform API, ACPs, console), which could be better modularized. Many tools are trivial variants (e.g., platform_get_block vs platform_get_block_by_height) adding unnecessary bulk.
The server provides thorough read-only coverage for Avalanche: docs search, ACP management, on-chain lookups, indexed stats, platform API getters, and console flow guidance. While there is no transaction submission (likely intentional), the surface covers most queries a developer would need, with minor gaps like detailed token transfer history.
