Skip to main content
Glama

SouthPow crypto & market data

buy_coin_APR

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

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

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?

No annotations exist, so the description carries the whole burden, and it does more than most: it discloses the paid model with an exact price and chain, that no credentials are required, that failures are not billed, and the upstream data sources (Coinbase Exchange with Kraken cross-check). Gaps remain on latency, freshness/staleness of the quote, and rate limits.

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?

Front-loads 'Paid.' and then the data payload, price, and access constraints in a compact telegraphic sequence with no filler. The trailing raw URL is more useful for a human integrator than an agent and slightly breaks the flow, but nothing is wasted.

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 parameters, no annotations, and no output schema, the description is the only source of truth, and it covers billing, auth, provenance, and the returned fields. The main shortfall is that the return shape (JSON keys/types, timestamp fields) is only implied by a prose list rather than described.

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 avoids inventing parameter talk and instead spends its words on output fields and billing terms.

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 (APR/USD) and enumerates the payload: last price, 24h open/high/low, % change, 24h and 30d volume. That is enough to separate it from the hundreds of sibling buy_coin_* tools without opening a schema. It loses a point only because no verb frames the operation (e.g. 'fetch'/'returns'); the reader infers retrieval from the field list.

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?

Operational context is strong – 'Paid', '$0.05 USDC on Base', 'No account, no API key', 'Failed calls not charged' tell the agent the cost and auth posture before calling. However, there is no explicit when-to-use/when-not guidance and no mention of when a sibling such as buy_crypto_price would be preferable.

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