fuse_get_token_priceReturns the current USD price for an ERC-20 token tracked by Fusebox. Powered by the Fusebox SDK TradeModule.
| Name | Required | Description | Default |
|---|---|---|---|
| tokenAddress | Yes | Address of the ERC-20 token whose USD price should be returned. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states it returns the current USD price but fails to mention potential issues like the token not being tracked, whether the operation is costless, or any rate limits. The phrase 'tracked by Fusebox' hints at a constraint but does not explain what happens if the token is not tracked.
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 two sentences and 16 words, front-loading the main purpose. Every word adds value without fluff or repetition.
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 tool's simplicity (1 parameter, no output schema, no annotations), the description is minimal. It does not specify the output format (e.g., number with decimals) or behavior for unsupported tokens. The completeness is adequate but could be improved with a note on return type or error handling.
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 covers 100% of the parameter, describing 'tokenAddress' as the ERC-20 token address whose price is returned. The description adds context that the price is in USD and that it must be a Fusebox-tracked token, which slightly enhances understanding beyond the schema. Baseline 3 is appropriate given high schema coverage.
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 verb ('returns'), the resource ('current USD price for an ERC-20 token'), and the scope ('tracked by Fusebox'). It distinguishes this from sibling tools like 'fuse_get_token_price_change' or 'fuse_get_token_price_history' which serve different purposes.
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 does not provide any guidance on when to use this tool versus alternatives such as 'fuse_get_token_price_change' or 'fuse_trade_indicative_price'. No when-not or exclusion criteria are mentioned.
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.
Most tools have distinct purposes (e.g., balances, trades, staking, notifications), but there is some overlap, such as multiple trading quote tools and parallel EOA vs. smart wallet operations (e.g., send_erc20 vs smart_transfer_token). Descriptions generally clarify differences, so only minor confusion is possible.
All tools follow a consistent `fuse_<verb>_<noun>` pattern (e.g., `fuse_get_balance`, `fuse_send_native`). The notification sub-group uses `fuse_notification_<verb>_<noun>`, which is internally consistent. No mixed conventions or chaotic naming exist.
With 50 tools, the surface is very large and likely overwhelming for agents. Many tools could be combined (e.g., price history and change tools, or multiple notification CRUD tools). The count is excessive for the server's scope, reducing coherence.
The tool set covers a wide range of Fuse operations: token info, balances, staking, trading, ERC-4337 smart wallets, notifications, and contract interaction. The `fuse_explorer_query` tool provides a catch-all for additional explorer endpoints, filling most gaps. Minor missing explicit tools (e.g., block details) are mitigable.