getTopCollectionsByVolumeGet Bitcoin ordinal collections ranked by trading volume from Magic Eden. Use this when user asks about 'inscriptions with most volume', 'top trading collections', or 'hottest ordinal collections'.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of collections to return (max 50) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety. The description adds the data source (Magic Eden) and ranking basis, but no additional behavioral details such as pagination or return format. This matches the baseline with annotations present.
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: first states purpose, second gives usage examples. No redundant words, front-loaded verb and resource, and every sentence earns its place.
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 one-optional-parameter tool with strong annotations, the description is complete. It clearly explains what it returns (ranked by volume), the data source (Magic Eden), and usage triggers. No output schema exists, but the tool's simplicity makes this sufficient.
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 coverage is 100%, with the sole parameter 'limit' fully described in the input schema. The tool description adds no extra meaning about the parameter beyond the schema, so baseline 3 is appropriate.
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 a specific verb ('Get') and resource ('Bitcoin ordinal collections ranked by trading volume from Magic Eden'), distinguishing it from siblings like getTopCollectionsByFloor or getTopBRC20ByVolume.
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?
Provides explicit trigger phrases ('inscriptions with most volume', 'top trading collections', 'hottest ordinal collections') to guide when to use. Does not mention alternatives or when-not-to-use, but the context is clear enough to select appropriately among siblings.
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.
With 113 tools spanning many chains and asset classes, there is substantial overlap. For example, listPositions and getAllPositions appear to serve the same function, and there are many balance, token discovery, and collection data tools that differ mostly by chain or protocol, making misselection likely.
Naming conventions are inconsistent: most tools use camelCase with a verb (baseGetBalances, ethSwapQuote), but some use underscores (nansen_defi_portfolio), others are just bare nouns (wallet, rugcheck), and there are irregularities like solanaBalances instead of solanaGetBalances, plus hederaTokensSwapQuote vs. baseSwapQuote.
The server exposes 113 tools, far beyond the typical well-scoped set. This is an extreme mismatch with the apparent purpose of a wallet/swap server, making discovery and selection difficult for agents.
While the server offers extensive read-only data (balances, market data, NFTs, positions), it lacks core write operations: there is no actual swap execution or token transfer tool, and the referenced emblemCreateVault tool is missing. These are significant gaps that will prevent agents from completing common wallet actions.