Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DIEM

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 burden and does well: it discloses the pay-per-call cost, the payment chain and currency, the absence of auth requirements, and the important billing behavior that failed calls are not charged. What it omits is update cadence/freshness of the quotes and any rate limits, which matters for a live-price endpoint.

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?

A single dense sentence-block with the cost flag and instrument front-loaded ahead of the field list and the endpoint URL, so nothing is buried. The telegraphic fragments ('Paid.', '(Coinbase Exchange, Kraken cross-check)') read compressed but every token carries information.

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 available, the description compensates by enumerating the returned metrics and naming the exchanges, so an agent knows what a successful response contains. Payment mechanics and failure billing are covered; only freshness/format details and sibling routing are left implicit.

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; the description correctly implies a parameterless call and adds no misleading parameter expectations. Nothing further is required to invoke it.

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 the exact resource (DIEM/USD live) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. It also names the data sources (Coinbase Exchange with Kraken cross-check), so an agent knows precisely what it is buying, and the asset pair differentiates it from the hundreds of sibling per-coin tools.

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?

The description supplies decision-relevant context (it is paid, costs $0.002 USDC on Base, needs no account or API key, and failed calls are free), which helps an agent decide whether to call. However, it never states when to prefer this over a generic sibling such as buy_crypto_price, nor any when-not-to-use condition or freshness/rate-limit guidance.

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