Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DNA

Paid. NeoSoul (DNA) 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/DNA.

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

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 does so well: it discloses the $0.05 USDC cost, both accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of stating rate limits, latency, or whether the charge is taken before or after the response.

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?

A single dense sentence covering cost flag, asset, returned fields, payment mechanics and endpoint URL. It is front-loaded with 'Paid' and the asset name, and no sentence is 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-param, no-annotations, no-output-schema price endpoint, the description covers cost, payment rails, auth requirements, failure billing and the returned fields, which is most of what an agent needs. Missing only the response encoding/format and the raw endpoint's exact request shape, which the agent may still need to construct the call.

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 nothing for the description to disambiguate; the baseline for a no-param tool applies. The schema's empty properties object is consistent with the description's implicit 'no arguments needed' framing.

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 (NeoSoul / DNA) and enumerates exactly what the call returns: live USD price, 24h change and market-cap rank. It is clearly distinguishable from the buy_coin_* and buy_tvl_* families, though it never states the operation as a verb (fetch/return), relying on the colon construction to imply it.

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 endpoint being the DNA price feed, and the payment conditions give practical context for when a call is appropriate. There is no explicit when-not guidance and no reference to a sibling such as buy_crypto_price or the generic pricing tools, so an agent must infer which price tool to pick.

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