Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DBR

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

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

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, the description carries the full burden, and it does well: it discloses that the call is paid ($0.002 USDC on Base), that no account or API key is required, and that failed calls are not charged. It does not cover rate limits, latency, or payment mechanics (e.g. how the USDC is settled), 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?

The telegraphic, front-loaded style puts cost first and the data payload second, so the most decision-relevant facts land early. It is dense but every clause carries information; only the raw URL at the end is marginal, since an agent cannot fetch it directly anyway.

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, no-output-schema tool, the description covers what matters: the returned fields, the price, the payment rail, the auth requirement, and the failure-charging policy. A brief note on response format or freshness would make it fully complete.

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; the baseline for a 0-param tool applies. The description correctly implies a no-argument call by giving a fixed endpoint URL.

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 resource (DBR/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume, plus the upstream sources. That is far more specific than the sibling names alone, which only vary by ticker. It stops short of 5 because it never states how it differs from the generic buy_crypto_price sibling.

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 DBR/USD scope and the 'No account, no API key' note, which tells an agent it can call this freely. But there is no explicit statement of when to prefer this over buy_crypto_price or when not to call it, and no note on caching or freshness expectations.

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