Skip to main content
Glama

get_coin_convert

Paid $0.02 (x402, USDC Base): convert an amount between assets at live USD spot (Coinbase) — e.g. 1 BTC = ? ETH. Rate + result in one call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_coin_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoAsset code, e.g. ETH
fromNoAsset code, e.g. BTC
amountNoAmount, default 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two non-obvious traits: the tool costs $0.02 via x402/USDC on Base, and rates come from Coinbase USD spot. However, it omits failure behavior for unknown or unsupported asset codes, rate freshness/latency, and whether a payment is charged on a failed conversion — important gaps for a paid mutation-adjacent call.

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?

One compact sentence with the cost and payment rail front-loaded before the purpose, then the return behavior. Every clause earns its place: price, protocol, data source, example, and result shape.

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

Completeness4/5

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

No output schema exists, yet the description covers the return ('Rate + result in one call'), the data source, and the cost. For a three-optional-parameter converter this is nearly sufficient; only error/edge-case behavior on invalid asset codes is left unstated.

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% and all three parameters (from, to, amount) are already documented including the amount default of 1. The description's '1 BTC = ? ETH' illustration mirrors the schema semantics but adds no new constraint such as supported asset universe, case sensitivity, or precision/rounding of the result.

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

Purpose4/5

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

States a specific verb and resource — 'convert an amount between assets at live USD spot (Coinbase)' — with a worked example ('1 BTC = ? ETH') that removes ambiguity. It is clearly distinct from single-price siblings like get_crypto_price or get_usd_price, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the conversion example and by 'Rate + result in one call', which tells the agent it gets both the rate and converted value in one round-trip. There is no explicit when-to-use vs when-not guidance, no mention of alternatives for plain price lookup, and no prerequisites beyond the implied payment.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources