Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DRB

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does a good job: it discloses that calls are paid, the exact price and payment rail (USDC on Base), that no account or API key is needed, and that failed calls are not charged. It omits rate limits, latency/refresh cadence, and response shape, which keeps it from a 5.

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?

Roughly two dense sentences with zero filler; the payload is listed first and commercial terms follow. The telegraphic fragments ('Paid.', '%', abbreviations) are efficient but read slightly like a spec sheet rather than prose, a minor cost to clarity.

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-parameter tool with no output schema, the description supplies what is otherwise missing: the exact data fields returned, the upstream sources, the payment terms, the auth requirement, and the failure-charging policy. An agent has everything needed to decide whether and how to call it.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the ticker is fixed in the endpoint rather than passed as an argument.

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 names the exact pair (DRB/USD) and enumerates the payload: last price, 24h open/high/low, % change, 24h and 30d volume, plus the source exchanges. There is no explicit verb ('returns'/'fetches'), and the tool name's 'buy_coin_' prefix suggests a purchase action rather than a data read, which slightly muddies intent. Still, an agent can tell exactly what data it gets.

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 'Paid. ... $0.10 USDC on Base. No account, no API key. Failed calls not charged.' line gives cost and access conditions that inform the decision to call, but there is no explicit when-to-use versus the free-looking sibling alternatives (buy_crypto_price, buy_coin_*). Usage is implied through the price/cost disclosure 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