Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DATA

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

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

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 the paid nature, exact price ($0.25 USDC on Base), that no account or API key is needed, that failed calls are not charged, and the underlying data sources (Coinbase Exchange with Kraken cross-check). It stops short of stating latency, rate limits, or error semantics beyond the no-charge guarantee.

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 but every clause carries information an agent needs (payload fields, sources, price, auth model, failure billing, URL). The leading 'Paid.' fragment is terse to the point of being cryptic, and the description is a single run-on rather than clearly separated purpose/payment sections.

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?

With no output schema, the description must enumerate return fields — and it does, along with payment mechanics and the endpoint URL, which is sufficient to invoke a zero-parameter tool correctly. Minor gaps are freshness guarantees and how payment is actually settled by the agent runtime.

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 schema contributes nothing and the baseline is 4. The description correctly implies the asset and payment rail are fixed, so an agent knows no arguments 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 enumerates exactly what is returned ('last price, 24h open/high/low, % change, 24h and 30d volume') for a specific pair (DATA/USD) and names the source venues. It does not use an explicit action verb like 'fetch' or 'buy', but the resource and payload are unambiguous, and the ticker-specific tool name already separates it from the hundreds of sibling buy_coin_* endpoints.

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 rather than stated: an agent can infer this is the endpoint for DATA/USD spot stats. There is no guidance on when to prefer this over the generic buy_crypto_price sibling or how it relates to the buy_coin_* family, and no note on data freshness or caching.

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