Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DCR

Paid. Decred (DCR) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/DCR.

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

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 solid job: it discloses the cost and chains accepted, that no account or API key is needed, and that failed calls are not charged — an unusually complete disclosure of failure and auth behavior. It does not describe latency, caching/freshness of the 'live' price, or the payment flow mechanics, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six short fragments, each carrying a distinct fact (what, cost, rails, auth, failure policy, endpoint). 'Paid.' is front-loaded so the agent sees the payment requirement before anything else, and there is no filler.

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 paid price lookup with no output schema, the description covers what is returned (spot price, 24h change, market-cap rank), the price of the call, acceptable payment chains, and failure billing. It omits the response shape and how settlement is actually executed, minor gaps given the tool's simplicity.

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 asset and endpoint are hardcoded and the description makes that clear by naming DCR and embedding the 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?

States a specific resource and payload: 'Decred (DCR) price: live USD price, 24h change and market-cap rank' — an agent knows exactly what data comes back. It stops short of differentiating itself from the many sibling price endpoints (buy_crypto_price, the buy_coin_* family), so the agent must infer this is the DCR-specific variant from the name alone.

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 token-specific name and the 'Paid' marker, and the payment/prerequisite context ($0.01 USDC on Base or Solana, no account, no API key) is genuinely useful. However there is no explicit when-to-use guidance and no mention of alternatives such as buy_crypto_price or the buy_coin_/buy_tok_ split, leaving the routing decision to inference.

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