Returns all active streaming swaps. Streaming swaps split large trades into smaller chunks executed over multiple blocks to minimize slippage. Supports pagination with limit and offset parameters.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return (default 100, max 1000) | |
| offset | No | Number of results to skip for pagination |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=false, so the safety profile is covered. The description adds a domain explanation of what streaming swaps are and notes pagination support, which is mildly useful context, but it omits rate limits, ordering, and result-shape behavior.
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?
Three sentences that front-load the operation, then the domain rationale, then pagination. The middle definitional sentence is somewhat tangential but aids selection; minimal waste overall.
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 read-only list tool with no output schema, the definition covers purpose, domain context, and pagination. It could route explicitly to get_streaming_swap, but nothing essential to correct invocation is missing.
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% and both parameters (limit, offset) are fully documented with defaults and max in the schema. The description merely repeats that pagination is supported via limit and offset, adding no format or interaction detail beyond the schema.
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 ('Returns all active streaming swaps') with a scope qualifier ('all active') that sets it apart from the singular get_streaming_swap sibling. It never names the sibling explicitly, so the distinction must be inferred rather than read.
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?
Usage is implied by 'all active' versus the singular get_streaming_swap, but the description never says when to use this rather than that, nor any prerequisites. No explicit when/when-not or alternative routing.
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.