Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DOT

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

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

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 the $0.05 USDC-on-Base cost, that no account or API key is required, that failed calls are not charged, the upstream data sources, and the endpoint URL. It stops short of rate limits, latency, or freshness guarantees, so it 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.

Conciseness5/5

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

Front-loaded with the payment signal ('Paid.'), then the payload, then provenance, then price/access terms, then the URL. Every clause carries a distinct fact and there is no filler; the telegraphic style suits a paid micro-endpoint.

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 paid data endpoint, the description enumerates the returned fields, sources, cost, auth model, and billing-on-failure policy — enough to decide and call correctly. The exact response shape (JSON keys, units, timestamp semantics) is not specified, which is the main remaining gap.

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 (empty, no required fields), so there is nothing for the description to disambiguate. Baseline 4 applies; the ticker is baked into the tool name rather than parameterized, which is consistent with the schema.

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 concrete resource and its payload: DOT/USD live last price, 24h open/high/low, % change, 24h and 30d volume, with named sources (Coinbase Exchange, Kraken cross-check). It is clearly distinguishable from siblings only via the ticker in the name, but the description makes the actual behavior explicit despite the misleading 'buy_coin' prefix.

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: this is the DOT price endpoint, so it is used when DOT/USD pricing is needed. However, it never names alternatives (e.g. buy_crypto_price, buy_coin_BTC for other assets) nor states when it should not be used, and the 'Paid.' framing does not explain when paying $0.05 is worthwhile versus a free source.

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