Skip to main content
Glama

SouthPow crypto & market data

buy_coin_PONS

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

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

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 that the call is paid, the exact price and payment rail (USDC on Base), that no account or API key is required, and that failed calls are not billed. Gaps remain on rate limits, data freshness/delay, and response format, which matter for a paid live-price call.

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?

The cost flag 'Paid.' is front-loaded where it matters most, followed by the payload, payment details, and endpoint. The style is telegraphic but every fragment earns its place; only the bare URL feels appended rather than integrated.

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 output schema and no annotations, the description compensates by listing the returned fields and naming the upstream sources (Coinbase Exchange with Kraken cross-check), which is exactly what an agent needs before spending money. It falls short of complete by omitting rate limits, data latency, and the shape of the response.

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 no parameter semantics to compensate for. The description correctly does not invent parameter discussion and instead spends its space on cost and payload.

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 states a specific asset pair and enumerates the exact data returned (last price, 24h OHLC, % change, 24h and 30d volume), so an agent knows precisely what this tool yields. It does not explicitly differentiate itself from near-identical siblings such as buy_crypto_price or the generic buy_coin_00, relying on the name to carry the asset identity.

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 context is implied by 'Paid' plus '$0.002 USDC on Base' and 'Failed calls not charged', which lets an agent judge cost risk, but there is no explicit when-to-use or when-not guidance and no named alternative for non-PONS or batch price lookups. The agent must infer that this is the per-asset endpoint for PONS only.

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