Skip to main content
Glama

SouthPow crypto & market data

buy_coin_RARE

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 behavioral burden and does well: it discloses the paid model, the exact price and payment chain, absence of auth requirements, the failure-billing policy ('Failed calls not charged'), and the data provenance (Coinbase Exchange, Kraken cross-check). Gaps are minor — no rate limits, latency, or freshness/staleness guarantees.

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 free of filler — cost and payload come first. The telegraphic fragments ('Paid.') and untagged trailing URL are slightly cryptic stylistically but everything present earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-param, no-output-schema, no-annotation tool the description must supply everything, and it does: return fields, data sources, cost, payment rail, auth posture, failure billing, and the endpoint. An agent can invoke and budget for this call without opening anything else.

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 there is nothing for the description to disambiguate; baseline applies. The description correctly signals that the asset is fixed by the tool rather than a parameter.

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 a specific resource (RARE/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. Against ~400 sibling buy_coin_<TICKER> tools, this makes the asset and payload unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear purchasing context — paid, $0.05 USDC on Base, no account or API key needed — which is what an agent needs to decide whether to call it. It does not, however, route against alternatives such as the more general buy_crypto_price sibling or explain when a free source should be preferred.

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