Retrieve all tokens available for swapping on Bitflow DEX to identify tradable assets without an API key.
Get all available tokens for swapping on Bitflow.
Returns the list of tokens that can be swapped on Bitflow DEX. No API key required — uses public endpoints (500 req/min).
Note: Bitflow is only available on mainnet.
Tip: call earning_opportunities to see how to put your assets to work.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.77.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and adds useful operational context: no API key required, public endpoints with a 500 req/min limit, and mainnet-only availability. It does not explicitly describe safety or error behavior, but 'Get' and 'Returns the list' make the read-only nature clear.
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 definition is short and front-loads the core purpose. The second sentence partly restates the first, and the closing tip about earning_opportunities is useful but not essential to invoking this tool.
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 zero-parameter list-retrieval tool, it covers the main constraints: mainnet-only, no API key, rate limit, and that it returns a token list. Without an output schema, it could say more about the token object fields, but the description is largely complete for selecting and invoking the tool.
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 tool has zero parameters, so there are no parameter semantics to document. The baseline for zero-param tools is 4, and the description adds no misleading parameter guidance.
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?
States a specific verb and resource: 'Get all available tokens for swapping on Bitflow' and clarifies the return is a token list on Bitflow DEX. It is clear, but does not explicitly distinguish itself from related siblings such as bitflow_get_swap_targets or bitflow_get_ticker.
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 intended use is implied by 'available tokens for swapping,' and it notes mainnet-only availability. However, it does not say when to use this instead of sibling token/swap discovery tools, nor does it provide explicit alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.