Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FUN1

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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, the exact price and payment chain, that failures are not billed, the upstream data sources (Coinbase Exchange with Kraken cross-check), and the raw endpoint. What is missing is staleness/latency, rate limits, and any note on what a failed response looks like.

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?

Everything is front-loaded — 'Paid.' leads so cost is known before anything else, then the returned fields, then payment terms, then the endpoint. It is telegraphic but every fragment (cost, data fields, no auth, refund policy, URL) carries distinct decision-relevant information with no repetition.

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 price tool, the description compensates well by enumerating the returned fields and their source exchanges. The only real gap is the absence of return-shape detail (units, timestamp field, error format), which an agent must discover by calling.

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 for a no-param tool applies. The description correctly does not invent parameter-like options, keeping the calling contract unambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and pair (FUN1/USD live) and enumerates exactly what comes back: last price, 24h open/high/low, % change, 24h and 30d volume. It also implicitly corrects the misleading 'buy_coin' verb by framing the tool as a read-only price lookup, letting an agent distinguish it from sibling token variants at a glance.

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?

Cost and access conditions ($0.002 USDC on Base, no account, no API key, failed calls not charged) give an agent the practical context needed to decide whether to call. However, it never states when to prefer this over the generic sibling buy_crypto_price, nor any exclusion or rate-limit condition that would route an agent elsewhere.

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