Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DAG

Paid. Constellation (DAG) 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/DAG.

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

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 full burden and mostly does: it declares the tool is paid, names the exact charge and accepted chains, states no auth is required, and clarifies that failed calls are free — all material for an agent deciding to spend money. It omits rate limits, latency, and freshness guarantees, which is a minor residual gap rather than a serious one.

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?

Front-loads the most decision-relevant fact ('Paid.') then asset, payload, price, and terms in a handful of compact clauses. No filler, no redundant restatement of the tool name, and the endpoint URL is appended where it does no harm.

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 price lookup, the description covers payload contents, cost, payment rails, auth, and failure billing — enough to invoke it correctly. The one omission is sibling differentiation against buy_coin_DAG and buy_crypto_price, which the surrounding tool list makes a real risk.

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 schema has zero parameters and 100% coverage, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies; no credit is needed or earned for parameter explanation.

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?

Names the specific asset (Constellation/DAG) and enumerates exactly what comes back: live USD price, 24h change, and market-cap rank. That is a clear verb-plus-resource statement. It never mentions how it differs from the very similar siblings buy_coin_DAG and buy_crypto_price, so an agent scanning the tool list has no basis for choosing among them.

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 (you want the DAG price) and the commercial terms are spelled out: $0.05 USDC on Base or Solana, no account, no API key, failures not charged. What is missing is routing guidance — no statement of when to pick this over buy_coin_DAG, buy_crypto_price, or the buy_tok_* family, which is the main ambiguity an agent faces here.

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