Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DYM

Paid. Dymension (DYM) 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/DYM.

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

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, the description carries the full burden and does a solid job: it discloses the exact cost ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It stops short of describing data freshness, latency, or the payment mechanism itself, so it is strong but not exhaustive for a paid endpoint.

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 critical fact ('Paid.') and then layers payload, price, access terms, and endpoint URL in a dense, scannable sequence. It is telegraphic rather than flowing prose, but nearly every clause adds actionable information and nothing is padded.

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?

With no output schema and no annotations, the description still tells the agent the three returned data points, the cost, the payment rails, and the failure-charging policy. The remaining gap is the concrete response shape (field names, numeric precision, timestamp), which an agent would have to discover by calling.

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. Nothing is left ambiguous about inputs, and the description correctly implies the coin is fixed by the tool name rather than passed as an 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 a specific resource (Dymension/DYM) and enumerates exactly what comes back: live USD price, 24h change, market-cap rank. The 'buy_tok_' prefix plus the explicit coin identity lets an agent distinguish it from the parallel buy_coin_* and buy_crypto_price families without opening a schema.

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 leading 'Paid.' plus the $0.05 price tag implies this is a purchase-style call, so an agent knows a cost is incurred. However, there is no explicit guidance on when to choose this over buy_crypto_price or the generic buy_coin_* endpoints, and no note on caching or repeated-call behavior.

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