Skip to main content
Glama

Get Swap Quote

get_quote
Read-onlyIdempotent

Obtain a price quote for token swaps showing expected output, exchange rate, and route. Works on Base, Citrea, HyperEVM, and Monad without authentication.

Instructions

Get a price quote for a token swap without authentication. Shows expected output amount, exchange rate, and route info. No wallet or session required — use this to check prices before committing to a swap. Supported chains: Base, Citrea, HyperEVM, Monad.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoTarget blockchain networkbase
amountYesAmount to quote (e.g. '0.1', '100')
slippageNoSlippage tolerance percentage (default: 0.5)
to_tokenYesDestination token symbol
from_tokenYesSource token symbol (e.g. 'ETH', 'USDC', 'MON')
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds beyond annotations: 'No wallet or session required' and lists supported chains. Discloses return fields (output amount, rate, route). Consistent with readOnlyHint and openWorldHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, no unnecessary words. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but description explains return fields (output amount, exchange rate, route info) and lists supported chains. Covers all necessary context for a quote tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description does not add new details for each parameter beyond general context. Schema descriptions already cover meaning adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get a price quote for a token swap' with specific verb and resource. It distinguishes from siblings like swap_tokens by noting no authentication and preview use. Supported chains are listed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance: 'use this to check prices before committing to a swap.' No authentication required, which informs when to use. Does not directly name alternatives but context makes it clear vs. swap_tokens.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Fibrous-Finance/fibx'

If you have feedback or need assistance with the MCP directory API, please join our Discord server