Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

coin-convert

[x402 paid: $0.010 USDC on Base] Convert amounts at live Coinbase rates (e.g. BTC to EUR, ETH to USD). tools/call returns the live payment challenge.

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": "coin-convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoexample: EUR
fromNoexample: BTC
amountNoexample: 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 does disclose the most important behavior: this is a paid x402 endpoint costing $0.010 USDC on Base, and that tools/call returns the live payment challenge. That payment-flow disclosure is genuinely valuable, but the description says nothing about whether the conversion is a quote or a stateful operation, how fresh or cached the rate is, or what happens on payment failure.

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 plus a bracketed cost marker, all front-loaded: price and payment model first, then capability, then invocation note. No filler and nothing repeated from structured fields.

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

Completeness3/5

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

For a 3-parameter tool with no annotations and no output schema, the description covers the payment model but omits the response shape and any failure/refund behavior, which the agent needs since no output schema exists. Adequate to attempt a call, not complete enough to predict its result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by showing how from/to pair up ("BTC to EUR") and confirming the semantic direction of the conversion. It still doesn't state that amount is a decimal string or what precision/asset codes are accepted, so it stops short of a 5.

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?

The description gives a specific verb plus resource ("Convert amounts") and names the rate source (live Coinbase rates) with two concrete examples (BTC to EUR, ETH to USD). It does not explicitly contrast itself with siblings like fiat-rates, crypto-price, or token-price, so an agent must infer the distinction, but the convert-amount framing is clear enough to be actionable.

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 rather than stated: the agent can infer this is the tool for converting an amount from one currency to another at live rates. There is no explicit when-to-use/when-not guidance and no named alternative for plain rate lookups, so the agent must reason about whether a sibling is more appropriate.

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