Get the minimum staking amounts for validators and delegators on a Subnet/L1
| Name | Required | Description | Default |
|---|---|---|---|
| network | No | Avalanche network to query (default: mainnet) | |
| subnetID | No | The Subnet ID to query minimum stake for (default: Primary Network) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. However, it only states what the tool does, not any behavioral specifics such as whether both validator and delegator amounts are returned, default behavior for missing parameters, or error conditions. It adds no information beyond the purpose, leaving the agent without crucial context for a read operation.
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?
The description is a single, succinct sentence that directly conveys the tool's function without unnecessary words. It is well-structured and front-loaded with the core action, making it easy to parse.
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?
Given the low complexity (2 optional params, no output schema, no annotations), the description is minimally adequate. However, it does not describe the return format or any caveats, and without output schema or annotations, it could be more complete. It suffices for a simple getter but leaves room for improvement.
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?
The input schema provides 100% coverage for both parameters, including descriptions and defaults (network default mainnet, subnetID default Primary Network). The tool description does not add any additional meaning beyond what the schema already conveys, so it meets the baseline but does not exceed it.
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 clearly states the tool's purpose: 'Get the minimum staking amounts for validators and delegators on a Subnet/L1'. It uses a specific verb (get) and resource (staking amounts) and scopes it to validators/delegators and Subnet/L1, distinguishing it from other platform_get* tools like platform_get_total_stake.
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?
The description provides no guidance on when to use this tool versus alternatives. It does not mention scenarios where other tools like platform_get_total_stake or platform_get_staking_asset_id would be more appropriate, nor does it offer exclusions or prerequisites. The name implies a specific use case, but explicit usage guidance is absent.
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.
