Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FOX

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

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

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, the description carries the full burden and does well: it discloses the paid model, exact price and chain, absence of account/API key requirements, that failed calls are not charged, and the upstream data sources (Coinbase Exchange with Kraken cross-check). The main gap is the payment mechanism itself (how the $0.25 USDC is collected, e.g. x402) and the response format.

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.' followed by the payload contents, then commercial terms — a sensible order for a metered call. The trailing endpoint URL is marginally useful, but overall there is little waste.

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 tool, the description compensates by enumerating the returned fields and the data provenance, plus the cost model. Only the payment flow and response encoding are unstated, which an agent would need before actually invoking.

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?

Zero parameters, so the baseline is 4. Nothing in the schema needs elaboration, and the description appropriately spends its words on the fixed ticker and payment terms instead.

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 and scope: live FOX/USD price with last price, 24h open/high/low, % change, and 24h/30d volume. It is distinguishable from the hundreds of buy_coin_<TICKER> siblings by the ticker, which is inherent in the name, but it never explicitly frames itself against the generic buy_crypto_price sibling.

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 context ('$0.25 USDC on Base', 'No account, no API key', 'Failed calls not charged') implicitly tell the agent this is a viable paid call without onboarding. However, there is no explicit when-to-use/when-not guidance, and no mention of the obvious alternative buy_crypto_price for agents that only need a generic quote.

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