Skip to main content
Glama

SouthPow crypto & market data

buy_coin_AUDIO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 substantial work: it discloses that the call is paid ($0.25 USDC on Base), that no credentials are needed, that failed calls are free, and which upstream venues supply the data (Coinbase Exchange with Kraken cross-check). It stops short of stating latency, rate limits, or whether the cross-check can alter reported values.

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 'Paid.' which is the single most decision-relevant fact, then the data payload, then cost/auth terms, then the endpoint. It is dense but every clause carries information; the only minor waste is an unpunctuated fragment style and a trailing bare URL.

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 tool with no output schema, the description must describe the return payload and it does, field by field. Payment mechanics and credential requirements are covered, leaving only response encoding and staleness/latency unspecified – minor gaps for a simple quote endpoint.

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 of 4 applies; there is no parameter semantics to document. The description correctly spends its words on output fields and payment terms instead of inventing parameter detail.

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?

States exactly what is returned for AUDIO/USD: last price, 24h open/high/low, % change, 24h and 30d volume. It also resolves the ambiguity created by the 'buy_coin_' prefix by making clear this is a live price data lookup, not a purchase, and pins the resource to a single coin unlike the many sibling variants.

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?

Usage is implied rather than directed – an agent can infer this is the AUDIO/USD quote endpoint, and the 'No account, no API key' line lowers invocation friction. However, there is no explicit when-to-use guidance, no mention of alternatives (e.g. buy_crypto_price or the sibling coin variants) and no when-not-to-use condition.

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