Skip to main content
Glama

Vibe Springs

by net.vibesprings
OverviewDiscussionsAdmin

convert_currency

Convert any amount between 30+ fiat currencies with real-time ECB rates. Returns converted amount, rate, and inverse rate. [PAID: $0.002 USDC per call via x402 on Base. First call without payment_signature returns the payment requirements.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesTarget currency ISO code (e.g. JPY, EUR)
fromYesSource currency ISO code (e.g. GBP, USD)
amountNoAmount to convert1
payment_signatureNoOptional x402 payment token. Call the tool WITHOUT this first to receive payment requirements (price, payTo, asset, nonce rules), sign the exact-scheme EIP-712 USDC authorization with your wallet, then retry with this field set to the base64 token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, but description discloses paid call cost ($0.002 USDC via x402), return structure (converted amount, rate, inverse rate), and data source (ECB). Does not cover error cases but is transparent about payment.

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?

Three concise sentences: purpose, return values, payment instructions. Front-loaded and no wasted words.

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, but description specifies return fields. Explains payment model. Missing details on error handling or edge cases, but sufficient for typical usage.

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%; description adds value by explaining the payment_signature two-step process and mentioning the range of currencies (30+ fiat).

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?

Describes conversion of any amount between 30+ fiat currencies using real-time ECB rates, clearly distinguishing from siblings like get_exchange_rates (which likely just provides rates) and other crypto-focused tools.

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?

Provides explicit two-step payment flow: call without payment_signature to get requirements, then retry with signature. Does not compare to alternatives but context is clear.

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

All Vibe Springs toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources