List the EVM chains a native gas balance can be emptied to exactly zero on. Returns chain IDs, names, and native tokens. Call this to check whether a specific chain is supported before quoting.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds return fields (chain IDs, names, native tokens) beyond annotations. Annotations already indicate readOnlyHint and openWorldHint. No contradictions.
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 sentences, front-loaded with purpose. Efficient and no wasted words.
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?
Complete for a parameterless listing tool. Describes what is returned and how to use it. No output schema needed.
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?
No parameters exist, so no need for parameter details. Baseline set to 4 for zero parameters.
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?
Clear verb 'List' and specific resource 'EVM chains a native gas balance can be emptied to exactly zero on'. Differentiates from sibling tools like zerodust_get_balances and zerodust_get_quote.
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 when to call: 'Call this to check whether a specific chain is supported before quoting.' Provides clear context for use. No explicit when-not, but purpose is clear.
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.
Each tool has a clear, distinct purpose: finding balances, listing chains, quoting sweeps, checking status, explaining concepts, listing history, and registering API keys. No overlap or ambiguity.
Most tools follow a consistent 'zerodust_verb_noun' pattern (e.g., get_balances, list_sweeps). 'info' is a slight deviation (single verb instead of verb_noun), but it's minor and still clear.
7 tools are well-scoped for the focused domain of recovering stranded gas tokens. Each tool serves a necessary function without redundancy.
Covers core workflows: discovery, pricing, status tracking, history, and explanation. The actual sweep execution requires a signing key, which is intentionally excluded from the hosted server (handled via SDK). Minor gap: no cancel/abort tool.