Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ANKR

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 the call is paid, the exact price ($0.25 USDC on Base), the payment rail, that no auth or account is required, and that failed calls are not charged. These are precisely the behavioral facts an agent needs before committing spend. It stops short of describing response format, latency, or whether pricing/staleness guarantees apply.

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?

Extremely dense with zero filler: payment status and price are front-loaded, followed by data content, sources, access requirements, billing behavior, and the endpoint URL. The telegraphic style suits a machine-read definition and every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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, no-annotation tool, the description covers what the agent needs: the exact dataset, its provenance (Coinbase with Kraken cross-check), cost and payment mechanism, auth requirements, and failure billing. Return value structure is largely conveyed by enumerating the fields, which compensates for the absent output schema.

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. The description correctly implies no inputs are needed by naming a fixed coin pair and a fixed endpoint URL, so nothing is missing on this dimension.

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 states a specific resource (ANKR/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume, plus the data sources. That is far more informative than the name alone. It doesn't distinguish itself from the generic sibling 'buy_crypto_price', leaving the agent to infer whether a per-coin tool or the generic one is preferred.

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?

Access conditions are clear (paid, no account, no API key, failed calls not charged), which implies 'use this if you're willing to pay $0.25'. But there is no explicit when-to-use/when-not guidance and no mention of the obvious alternative 'buy_crypto_price', so the choice between them is left to inference.

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