Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DG

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

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

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 zero annotations the description carries the full burden and does well: it discloses that the call is paid, the exact price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. Not disclosed are rate limits, how payment is actually settled (x402 handshake?), or latency.

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?

Roughly thirty words, front-loaded with the payment caveat ('Paid.') before purpose, then cost, then access conditions, then endpoint. Every clause carries distinct information an agent needs before spending money, and nothing is repeated.

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, zero-output-schema tool the definition is nearly self-sufficient: it says what is returned, what it costs, where payment is accepted, and that failures are free. The remaining gap is operational detail of the payment flow, which matters because an agent must actually spend funds to invoke 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 input schema has zero properties, so per the baseline this dimension starts at 4. There is nothing for the description to clarify about parameters, and the contract-described fields (price, change, rank) describe the return payload rather than inputs.

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 (DeGate / DG token) and enumerates exactly what data comes back: live USD price, 24h change, market-cap rank. That is far more than the name alone conveys. It stops short of a 5 because it never explicitly tells the agent that this symbol-specific tool is one of hundreds of identical per-token siblings and that other tickers need their own tool.

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 conditions are implied by the symbol in the name and the '$0.05 USDC' price line, and 'No account, no API key' answers the main prerequisite question. However, there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as buy_crypto_price or the buy_coin_* family for a general or different-asset price check.

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