Skip to main content
Glama

SouthPow crypto & market data

buy_coin_VTHO

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

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

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 provided, the description carries the full burden and does a solid job: it discloses the cost ($0.002 USDC on Base), the payment rail, that no account or API key is required, that failed calls are not charged, and which exchanges feed the data. It stops short of stating response format, refresh latency, or rate limits.

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?

Front-loaded with 'Paid.' then the highest-value information (what data, what cost), with the endpoint URL last where it belongs. The telegraphic style packs a lot into four short fragments; only the bare '$0.002 USDC on Base' would benefit from slightly more framing.

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 tool with no output schema, the description must describe the payload, and it does list the returned fields. Missing pieces are minor for this complexity: no indication of response shape (JSON keys), latency, or numeric precision—all of which an agent might want before paying.

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 and the description correctly avoids inventing any. It also pre-empts the natural question about parameterization by embedding the ticker in the URL.

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?

States a specific verb and resource: live VTHO/USD price with an explicit field inventory (last, 24h open/high/low, % change, 24h and 30d volume) and names the data sources. It is distinguishable from the ~400 sibling buy_coin_<TICKER> tools by the embedded VTHO/USD pair, though it never explicitly says 'this covers only VTHO' or points to the generic buy_crypto_price alternative.

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 mention of live quotes and cross-checked sources tells an agent this is a read-only quote lookup. There is no explicit when-to-use guidance, no mention of when to prefer buy_crypto_price, and no note about whether data is fresh enough for trading decisions.

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