Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DUAL

Paid. Dual (DUAL) 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/DUAL.

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

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 well: it discloses the flat $0.01 USDC cost, the two accepted chains (Base, Solana), that no account or API key is required, and that failed calls are not charged — the key financial risk facts. It omits rate limits, latency, and what constitutes a 'failed' call, which keeps it below the top band.

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 clauses, front-loaded with the billing flag 'Paid.' and then purpose, price, prerequisites, refund policy, and endpoint. Every sentence carries distinct, actionable information with no 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 paid lookup with no output schema, the description covers the required ground: what it returns, what it costs, how to pay, and that auth is unnecessary. Slightly short of complete because it does not describe the response shape (JSON fields, units) or what happens when the payment itself fails.

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?

Zero parameters, so nothing needs semantic explanation and the baseline is 4. The description correctly implies the token is fixed by the endpoint rather than passed as an argument, which removes any temptation to invent a symbol parameter.

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?

States a specific resource (DUAL token) and concrete payload (live USD price, 24h change, market-cap rank), so an agent knows exactly what comes back. It never explains the difference between the buy_tok_* family and the large buy_coin_* family, but no buy_coin_DUAL sibling exists to confuse it with, so the ambiguity is low.

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?

'Paid' plus the price and payment rails sets the context for when a call is warranted, implicitly telling an agent to spend only when a live DUAL quote is needed. There is no explicit when-not-to-use, no mention of chatty callers or caching, and no comparison against the buy_crypto_price or buy_coin_* alternatives.

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