Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DNT

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

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

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 supplied, the description carries the full burden and does well: it discloses that the call is paid ($0.05 USDC on Base), requires no account or API key, and that failed calls are not charged. That is genuinely decision-relevant behavior an agent could not infer from the schema. It omits how payment is actually settled and any rate limits or latency expectations.

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?

Front-loads the single most important constraint ('Paid.') and then packs fields, cost, auth, and endpoint into a few sentences with no filler. The telegraphic style is dense but every clause carries information; the bare URL at the end is the only element that could be considered supplementary.

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 tool with no output schema, the description compensates reasonably by enumerating the returned fields and naming the upstream data sources. Remaining gaps are the exact response shape (units, JSON keys) and how the USDC-on-Base payment is executed, which matter because there is no output schema or annotations to fall back on.

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 no parameter meaning to add and the baseline is 4. The description correctly adds no phantom parameter guidance and focuses on what the call returns instead.

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 a specific resource and scope: 'DNT/USD live' with an explicit field list (last price, 24h open/high/low, % change, 24h and 30d volume). It is clearly distinguishable from generic siblings like buy_crypto_price, though differentiation from the other 300+ buy_coin_<TICKER> variants rests entirely on the ticker token rather than any stated distinction.

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 'live' price data and data sources (Coinbase Exchange, Kraken cross-check), but the description never says when to pick this per-coin endpoint over the generic buy_crypto_price sibling, nor does it state any exclusions. The buying/commercial conditions are stated, but that is pricing, not usage 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