Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BSV

Paid. Bitcoin SV (BSV) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/BSV.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the call is paid, the exact price and accepted chains, that no account or API key is required, and that failed calls are not charged. It omits data freshness/latency and any rate-limit or retry behavior, which keeps it short of 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?

It is a compact block: the paid flag leads, the resource and returned fields follow, then payment terms and the endpoint URL. Every clause carries information, though the raw URL sits awkwardly at the end rather than after the payment terms where it is more actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, single-datum paid endpoint with no annotations and no output schema, the description covers everything an agent needs: what it returns, what it costs, on which chains, that no credentials are needed, and the failure-billing policy. No structural gaps remain.

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 input schema is an empty object with no properties, so there is nothing for the description to clarify. Baseline 4 applies for a zero-parameter tool, and the description correctly signals no inputs are needed.

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 names the resource (Bitcoin SV / BSV) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. That is far more specific than a bare restatement of the name. It does not, however, distinguish this from adjacent siblings such as buy_coin_* or buy_crypto_price, so an agent must infer which family to pick.

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 by the stated purpose, and the cost/payment prerequisites ($0.05 USDC on Base or Solana, no account, no API key) are useful decision inputs an agent can weigh before calling. There is no explicit when-to-use or when-not-to-use guidance and no named alternative for the same data.

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