Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DUSK

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so well: it flags that the call is paid, quantifies the cost ($0.01 USDC), names the accepted payment rails (Base or Solana), states no account or API key is needed, and clarifies that failed calls are not charged. Those are precisely the facts an agent needs before invoking a metered endpoint.

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?

Five short fragments, front-loaded with 'Paid.' and the resource, followed by cost, auth, and failure semantics, then the endpoint URL. Nothing is wasted; even the URL is load-bearing for an agent doing direct HTTP payment.

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 tool with no output schema, the description does the heavy lifting by naming the returned fields (price, 24h change, market-cap rank) and covering payment, auth, and failure charging. It stops short of describing the response format (JSON shape), freshness/latency, or how the USDC payment is actually settled, which are the remaining gaps.

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; baseline 4 applies. The description correctly implies no arguments are required by describing the call as a plain resource fetch.

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?

The description gives a concrete resource and payload: 'DUSK (DUSK) price: live USD price, 24h change and market-cap rank', which is specific enough that an agent knows exactly what it gets. It does not route against siblings — nothing distinguishes it from buy_crypto_price (a general price tool) or explains that this is the per-token variant of the buy_tok_* family.

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 only implied: an agent infers it should call this when it needs a DUSK quote. There is no explicit when-to-use vs when-not guidance and no pointer to buy_crypto_price or other price tools as alternatives, which matters given the hundreds of near-identical siblings.

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