Skip to main content
Glama

SouthPow crypto & market data

buy_coin_VVV

Paid. VVV/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.01 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/VVV.

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": "buy_coin_VVV"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/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 well: it discloses the cost ($0.01 USDC on Base), that no account or API key is needed, that failed calls are not charged, and the upstream data sources. It omits rate limits, latency, and response format, which keeps it below a 5.

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

Conciseness4/5

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

Dense but efficiently front-loaded — payment model first, then payload fields, then price/auth/error terms, then URL. The telegraphic fragments ('Paid.', 'No account, no API key.') are slightly staccato but every clause carries real information.

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?

For a zero-parameter, no-output-schema price endpoint, the description covers the key facts an agent needs to call it: what data comes back, what it costs, what credentials are needed, and failure billing. Only response format/units and rate limits are missing.

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?

The tool takes zero parameters, so the baseline is 4. The description confirms no inputs are needed by stating no account or API key is required, and there is nothing further for it to explain.

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 makes clear this returns VVV/USD market data (last price, 24h open/high/low, % change, 24h and 30d volume) sourced from Coinbase Exchange with a Kraken cross-check, which resolves the ambiguity of the 'buy_coin_VVV' name. It doesn't explicitly state the verb ('returns'/'fetches') or how it differs from the generic sibling buy_crypto_price, but the ticker scoping is unmistakable.

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: a paid, single-ticker price endpoint that costs $0.01 USDC, so an agent can infer it is for VVV quotes specifically. There is no explicit when-to-use or when-not guidance — notably no routing versus the generic buy_crypto_price sibling or the other buy_coin_* tickers.

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