Skip to main content
Glama

SouthPow crypto & market data

buy_coin_TREE

Paid. TREE/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.01 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/TREE.

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

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 supplied, the description carries the full burden and does well: it discloses that the call is paid ($0.01 USDC on Base), needs no auth, is not charged on failure, and draws from Coinbase Exchange with a Kraken cross-check. What it omits is data freshness/latency, rate limits, and the shape of the response.

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-loaded with the billing flag ('Paid.') and then the payload, with no filler sentences. The telegraphic field-list style is dense but readable, and each clause (cost, auth, sources, failure policy) earns its place.

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 annotations and no output schema, the description must cover everything, and it handles the commercial and sourcing dimensions that an agent cannot infer. It falls short only on response format and freshness/refresh cadence, which matter for a live price feed but are not stated.

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 there is nothing for the description to disambiguate. The baseline of 4 applies; the URL line at least tells an agent the call is fully parameterized by the path.

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 (TREE/USD) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. That distinguishes it from the hundreds of sibling buy_coin_* token tools without opening a schema, though it never states a verb such as 'fetch' or 'returns'.

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?

It supplies useful preconditions (no account, no API key, failed calls not charged, $0.01 USDC on Base) but never says when to pick this over alternatives such as buy_crypto_price or a generic price feed. The cost note implies 'pay only when you need this specific pair', which is implied usage rather than explicit guidance.

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