Skip to main content
Glama

SouthPow crypto & market data

buy_coin_VIRTUAL

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

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

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 that the call is paid ($0.10 USDC on Base), requires no auth, is not charged on failure, and where the data comes from (Coinbase Exchange with Kraken cross-check) plus the endpoint URL. It omits latency, rate limits, and caching/freshness guarantees, so behavior is strong but not exhaustive.

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?

Extremely dense and front-loaded – 'Paid.' leads so the cost signal hits first, then data fields, then payment/auth terms, then URL. It is telegraphic rather than prose, and the bare URL tail is a bit abrupt, but almost every token earns its place.

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-param, annotation-free tool with no output schema, the description covers what is returned (field list), where data originates, the commercial terms, and failure handling – enough for an agent to call it correctly. The main remaining gap is response shape/format and freshness, which matter since no output schema exists to explain them.

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, which is the baseline-4 case. There is nothing for the description to disambiguate, and it correctly avoids inventing parameter discussion.

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 concrete resource and verb-adjacent scope: 'VIRTUAL/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', so an agent knows exactly which data it gets. The ticker-scoped naming already separates it from the hundreds of sibling buy_coin_* tools, but the description never says 'this returns price data for VIRTUAL only' in a way that frames the family relationship explicitly.

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?

Gives clear conditions for calling it ('No account, no API key', 'Failed calls not charged') and the cost, which helps an agent judge willingness to pay. It offers no explicit when-to-use vs. when-not guidance against alternatives such as buy_crypto_price or the other buy_coin_* tickers, leaving the choice to the caller's inference.

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