Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CVX

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

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_CVX"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 paid cost and payment chain, that no account or API key is needed, that failed calls are not charged, and that data comes from Coinbase Exchange with a Kraken cross-check. It omits rate limits, latency/refresh cadence, and how the USDC payment is presented on the request.

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?

Very dense for its length: cost and payment first, then returned fields, then sources, then access requirements, then URL. The telegraphic phrasing ("Paid.", "No account, no API key.") is efficient but a touch clipped; nothing is wasted.

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?

There is no output schema, so listing the returned metrics in the description is necessary and done here, along with sourcing and billing behavior. The only remaining gap is operational detail such as refresh cadence and payment mechanics for a paid endpoint.

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 there is nothing for the description to disambiguate beyond asset scope, which it does by naming CVX in the title field listing. Baseline 4 applies to parameter-free tools.

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?

"CVX/USD live: last price, 24h open/high/low, % change, 24h and 30d volume" names a specific resource, the exact fields returned, and the ticker that separates it from the hundreds of sibling buy_coin_* tools. An agent can tell instantly which asset this covers.

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?

Leading with "Paid" and "$0.05 USDC on Base" gives a cost signal before invocation, and the source line implies this is the tool for spot CVX price data. However, it never states when to prefer this over a generic price sibling like buy_crypto_price, nor any condition where it should not be used.

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