Skip to main content
Glama

SouthPow crypto & market data

buy_coin_TAO

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

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

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 supplied, the description carries the full disclosure burden and does well: it states the charge ($0.05 USDC on Base), that no account or API key is required, and that failed calls are not charged, plus the upstream data sources (Coinbase Exchange with Kraken cross-check). What it omits is anything about the response shape or units, or what a failure looks like, so it falls short of full behavioral coverage.

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?

Five short fragments, each carrying distinct information: payment status, data payload, sources, price, auth requirements, failure policy, endpoint. The cost caveat is front-loaded with 'Paid.' and nothing is redundant.

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-annotation tool with no output schema, the description covers the commercial and operational essentials an agent needs before spending money. The remaining gap is that the return format and freshness/latency are not described, which matters slightly more here because there is no output schema to fall back on.

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 and there is nothing for the description to disambiguate. The mention of the endpoint URL is a small bonus since it tells the agent the call is parameterless by design.

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 a specific resource (TAO/USD) and enumerates exactly what data comes back: last price, 24h open/high/low, % change, and 24h plus 30d volume. The ticker in the name plus the explicit 'TAO/USD' line separates it cleanly from the hundreds of sibling buy_coin_* tools. It stops short of a 5 because the operative verb is only implied by the name ('buy') rather than stated in the description itself.

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?

'Paid.' plus the $0.05 price signals the cost context, and 'No account, no API key' tells the agent it can call this without setup. However, there is no explicit when-to-use or when-not guidance, and no routing to alternatives such as buy_crypto_price or the other buy_coin_* variants. The selection logic is left to the agent's inference from the ticker.

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