Skip to main content
Glama

SouthPow crypto & market data

buy_coin_WRON

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

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

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 at all, the description carries the full behavioral burden and does unusual well here: it discloses pay-per-call pricing ($0.10 USDC on Base), that no account or API key is needed, that failed calls are not charged, and the upstream data sources plus Kraken cross-check. What it omits is response format (JSON shape), data freshness/update cadence, and latency.

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?

Front-loaded with the most decision-relevant token ('Paid.') and then packed with facts in short clauses — no filler, no restatement of the tool name, and the endpoint URL placed last as reference rather than lead content.

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 annotations and no output schema, the description substitutes for the missing output schema by listing exactly which price and volume fields come back. It falls short only on response format and error semantics, which an agent must infer before parsing the result.

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 per the baseline this scores 4; there is nothing for the description to disambiguate. The description instead spends its words on what the call returns, which is the only semantic gap a parameterless tool can have.

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 the exact asset pair (WRON/USD) and enumerates the returned data: last price, 24h open/high/low, % change, 24h and 30d volume. Combined with the ticker in the tool name, an agent can distinguish this from the hundreds of sibling per-coin tools without opening any schema.

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 by the asset-specific name and the stated output, but there is no explicit when-to-use guidance, no mention of the nearest alternatives (buy_crypto_price, buy_coin_00), and no stated conditions under which this tool should not be used. The cost and no-account notes help an agent decide whether it can afford to call, but not which tool to choose.

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