Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DYNA

Paid. Dynachain (DYNA) 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/DYNA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full burden and does a solid job: it discloses the paid nature, the exact cost, the two accepted payment rails, that no account or API key is required, and that failed calls are not charged. Remaining gaps are the response format and any rate limits, but the economically important behavior (cost exposure) is fully disclosed.

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 fact that the call is paid and what it returns, then layers cost, auth and endpoint in descending order of decision relevance. It is telegraphic and every clause carries information, though 'Paid.' followed by the price restatement is mild redundancy.

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 price lookup with no annotations and no output schema, the description covers everything an agent needs before calling: what data comes back, what it costs, how to pay, that no credentials exist, and the endpoint. Only the concrete response shape is left implicit, which is a minor gap.

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 per-parameter semantics to explain and the baseline is 4. The description correctly implies the target token is baked into the tool rather than passed in, so an agent will not look for a symbol argument.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the exact resource (Dynachain / DYNA) and enumerates the payload: live USD price, 24h change and market-cap rank. That verb-plus-resource specificity lets an agent distinguish it from the hundreds of sibling buy_tok_* and buy_coin_* price tools.

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?

The description makes clear this is a paid lookup and states the price ($0.05 USDC on Base or Solana) and that failures are free, which implicitly tells the agent when it is safe to call. However, it never states when to prefer this over alternatives such as buy_crypto_price or the buy_coin_* family, and gives no guidance on caching or repeated calls.

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