Skip to main content
Glama

defi_swap_quote

Get a swap quote on a decentralized exchange. Input source token, target token, and amount to receive the estimated output.

Instructions

[DeFi] DEX兑换报价 — $0.03/call (free tier: 50/50 today) API: https://goldbean-api.xyz/paid/defi-swap-quote

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromTokenYes源代币
toTokenYes目标代币
amountYes数量
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, idempotency, side effects, or authorization requirements. The user must infer that it is a quote (presumably safe read), but this is not explicit.

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

Conciseness3/5

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

The description is short but includes extraneous pricing info (e.g., '$0.03/call') and API URL that may not aid tool selection. It could be more focused on functionality. It is front-loaded with category label but loses conciseness due to clutter.

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

Completeness2/5

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

Given 3 parameters and no output schema, the description should explain what the quote represents (e.g., estimated output amount, price impact) and return format. It does not, leaving the agent without key context to interpret results.

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?

The input schema has 100% description coverage with Chinese names for fromToken, toToken, and amount. The description adds no additional meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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

Purpose3/5

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

The description includes 'DEX兑换报价' which roughly translates to 'DEX exchange quote', indicating the tool provides a swap quote. However, it lacks a clear verb like 'get' or 'fetch', and the title is null. The purpose is implied but not explicitly stated.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs other DeFi sibling tools like defi_insights, defi_pool_stats, or defi_lending_rates. The description only mentions pricing and an API URL, not usage context or alternatives.

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/wuzenghai616-lang/goldbean'

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