Get a read-only Paraswap price quote on Base. The response identifies the actual venues returned by Paraswap. No transaction construction, execution, custody, or fee collection.
| Name | Required | Description | Default |
|---|---|---|---|
| tokenIn | Yes | Input token symbol on Base. One of: ETH, WETH, USDC, USDT. | |
| amountIn | Yes | Amount of input token. Must be greater than 0. | |
| tokenOut | Yes | Output token symbol on Base. One of: ETH, WETH, USDC, USDT. |
Changes observed during successful MCP inspections.
Input schema / properties / chainRemoved value: -{
- "description": "Preferred chain: base (Uniswap/OKX) or solana (Jupiter). Omit to quote all.",
- "type": "string"
-}Input schema / properties / tokenIn / descriptionPrevious value: -"Input token symbol. One of: ETH, WETH, USDC, USDT, SOL."New value: +"Input token symbol on Base. One of: ETH, WETH, USDC, USDT."Input schema / properties / tokenOut / descriptionPrevious value: -"Output token symbol. One of: ETH, WETH, USDC, USDT, SOL."New value: +"Output token symbol on Base. One of: ETH, WETH, USDC, USDT."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true, and the description reinforces this while adding specific behavioral context: the response identifies actual venues returned by Paraswap, and there is no transaction construction, execution, custody, or fee collection. This adds value beyond annotations without contradicting them.
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, front-loaded with the core purpose, and every sentence earns its place by adding meaningful constraints. It is concise without losing necessary clarity.
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?
The tool is simple with three well-documented parameters and clear read-only semantics. The description additionally mentions the response identifies venues, which partially compensates for the lack of an output schema. It is sufficiently complete for a straightforward quote 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?
Schema description coverage is 100%, and each parameter is already described in the schema. The description adds little parameter-level detail beyond confirming asset symbols and the Base network, so a baseline score of 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 the tool gets a read-only Paraswap price quote on Base, with a specific verb and resource. It also distinguishes what the tool does not do (no transaction construction, execution, custody, or fee collection), making the purpose unambiguous.
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 provides clear context that this is for obtaining quotes only, explicitly excluding transaction creation and fee handling. It lacks explicit alternative tool names, but the absence of siblings and the clear read-only scope give adequate usage guidance.
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.