Skip to main content
Glama

SouthPow crypto & market data

buy_coin_C98

Paid. C98/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/C98.

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

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, the description carries the full burden and does well: it discloses that calls are paid ($0.05 USDC on Base), that no account or API key is required, that failed calls are not charged, and where the data comes from (Coinbase Exchange with Kraken cross-check). It omits rate limits, latency, and whether successful calls are billed per invocation, but the cost/failure model is unusually well covered.

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

Conciseness5/5

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

Telegraphic but front-loaded: payment status leads, then the data payload, then cost/auth/failure terms, then the URL. Every fragment conveys distinct information with no filler, which is appropriate for a single-purpose endpoint tool.

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 tool, the description enumerates the returned fields, the data providers, the price, the auth requirement, and the failure-billing policy, which is enough to call it correctly. Minor gaps remain around rate limits and response format, but the essential decision inputs are present.

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 and the baseline of 4 applies. The description correctly implies no input is needed by directly stating the symbol and endpoint.

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 exact resource (C98/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. That is far more specific than the bare tool name. It does not mention the generic sibling buy_crypto_price or explain when to prefer a per-symbol endpoint, so sibling differentiation is only implied by the symbol embedded in the name.

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 context is implied by listing the exact market data available, and the payment/auth prerequisites ('$0.05 USDC on Base', 'No account, no API key') are stated. However, there is no explicit when-to-use versus when-not-to-use, and no pointer to alternatives such as the generic buy_crypto_price tool. The agent must infer that this is the C98-specific quote endpoint.

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