Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ROSE

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

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

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 provided, the description carries the full burden and does well: it discloses that the call is paid, the exact price and payment rail ($0.05 USDC on Base), that no account or API key is needed, and that failed calls are not charged. It omits rate limits, what constitutes a failure for refund purposes, and whether the Kraken cross-check is automatic or conditional — but the money/auth behavior, the riskiest unknowns, are covered.

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?

Dense, front-loaded, and almost every fragment earns its place: data scope first, then price/payment, then auth, then refund policy, then endpoint URL. The telegraphic style ('Paid.') and the packed field enumeration are readable but slightly choppy; a little more connective structure would improve scanability without adding length.

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?

Because there is no output schema, the description must describe return contents — and it does, listing the price, OHLC, change, and two volume windows. Payment, authentication, and failure-charging behavior are all stated, which is what an agent needs before committing money. Gaps remain around response shape/units, latency, and stale-data handling, but these are secondary for a zero-parameter paid read.

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 schema can add no semantics and the description has nothing parameter-level to explain. Per the baseline for parameterless tools, this sits at 4; the field list in the description describes outputs rather than inputs and so does not add parameter meaning, but nothing is missing either.

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 specifies the exact asset pair (ROSE/USD) and enumerates the returned data: last price, 24h open/high/low, % change, 24h and 30d volume, with named sources (Coinbase Exchange, Kraken cross-check). That cleanly separates it from the hundreds of sibling buy_coin_<TICKER> tools by ticker. It loses a point because the tool name implies a purchase while the description describes a paid price-data retrieval, leaving a mild name/behavior mismatch the text only implicitly resolves.

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?

It gives real operational context ('Paid', '$0.05 USDC on Base', 'No account, no API key', 'Failed calls not charged') that helps an agent decide whether it can call this at all. However, it never says when to prefer this over the obvious alternative, the generic sibling buy_crypto_price, nor any when-not-to-use condition or freshness/caching caveat. Usage is implied by the asset pair rather than stated.

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