Skip to main content
Glama

Vibe Springs

by net.vibesprings

get_crypto_prices

Live cryptocurrency prices, market caps, volume, and percentage changes for top tokens. Supports custom coin lists and multiple quote currencies. [PAID: $0.005 USDC per call via x402 on Base. First call without payment_signature returns the payment requirements.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vsNoQuote currency: usd, eur, gbp, jpy, btc, ethusd
idsNoComma-separated CoinGecko IDs (e.g. bitcoin,ethereum). Omit for top coins.
limitNoMax results
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. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and discloses that the tool is paid ($0.005 USDC per call via x402 on Base) and explains the two-step payment flow. This adds essential behavioral context beyond what the schema provides.

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?

The description is two sentences (plus payment detail in brackets), front-loaded with the main functionality, and contains no fluff. Every sentence contributes meaning.

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?

The description sufficiently covers the tool's inputs (custom coin lists, quote currencies) and outputs (prices, market caps, volume, percentage changes). Given the absence of output schema, it provides enough context for an agent to understand the return data type.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining the overall data returned and the payment_signature parameter's behavior, which goes beyond the schema's individual parameter descriptions.

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 the tool returns live cryptocurrency prices, market caps, volume, and percentage changes for top tokens, supporting custom coin lists and multiple quote currencies. This distinguishes it from sibling tools like get_crypto_news.

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?

The description implies usage for price data and mentions the payment requirement, but does not explicitly state when to use this tool versus alternatives like get_crypto_news or get_defi_yields. It provides clear context but lacks explicit exclusions.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes, but get_crypto_prices overlaps partially with get_market_pulse (which includes crypto prices), and get_exchange_rates overlaps with convert_currency. Descriptions clarify boundaries, but minor confusion possible.

Naming Consistency4/5

Nearly all tools follow a get_<noun> or verb_noun pattern, with consistent snake_case. The only outlier is 'health' which is a single word, but it still fits as a status endpoint.

Tool Count4/5

22 tools is slightly high for a single server, but each tool offers a distinct paid endpoint and the variety justifies the count. The server would benefit from a bit more focus, but it's still acceptable.

Completeness4/5

The server covers a wide range of data (crypto, weather, finance, on-chain risk, travel) with search and health endpoints. Missing operations like delete_watch or list_watches are minor gaps, but core functionality is well represented.

Resources