Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SKY

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

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

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 $0.25 USDC-on-Base cost, that no account or API key is required, and that failed calls are not charged — all non-obvious operational traits. It omits rate limits, latency, and the response format, which prevents 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?

The description is telegraphic and front-loaded, leading with 'Paid.' and then the payload, so an agent learns cost and content within the first two clauses. Minor redundancy between 'Paid.' and the '$0.25 USDC on Base' clause, but every sentence carries operational information (sources, payment, auth, failure policy, endpoint URL).

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 is nearly sufficient: it enumerates the fields returned, names the upstream exchanges, and states the payment and auth model. The exact response shape (JSON keys, units, timestamp/quote currency) is left unspecified, 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, so the baseline is 4; there is nothing for the description to disambiguate. It correctly focuses its budget on the return content instead of inventing parameter guidance.

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 (SKY/USD) and enumerates the returned data points: last price, 24h open/high/low, % change, and 24h/30d volume. It does not use an explicit verb like 'fetch' or 'retrieve', but the ticker specificity distinguishes it from the hundreds of buy_coin_<TICKER> siblings. The only ambiguity is the name 'buy_coin_SKY', which suggests a purchase while the description describes a paid price-data lookup.

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 data listing (use this to get live SKY price), but there is no explicit statement of when to prefer it over a sibling such as buy_crypto_price or another ticker variant, and no when-not-to-use guidance. The mention of Coinbase Exchange with a Kraken cross-check hints at data sourcing but not at selection criteria.

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