Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DOVU

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 price ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — a meaningful error/billing behavior. It omits how payment is actually attached to the request and what a failure response looks like.

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?

Four very short sentences, front-loaded with the payment status and then the payload, with the endpoint URL last. No filler, though the bare price/network fragments read as telegraphic rather than fully formed guidance.

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, no-output-schema price feed, the description covers the returned fields, cost, settlement chains, auth requirement, and endpoint. The only gap is the exact response shape and how the paid call is authorized, which the absent output schema would otherwise have covered.

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 schema has zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies the token is fixed by the endpoint URL rather than passed as an argument.

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 and payload: 'DOVU (DOVU) price: live USD price, 24h change and market-cap rank', which tells an agent exactly what data comes back. It is clearly distinguishable from the many buy_coin_* siblings since it names the token and the field set, though it never explains the 'buy_tok_' purchase wrapper itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative (e.g. buy_crypto_price or a buy_coin_* sibling) for agents that want a free or multi-token quote. The 'Paid.' prefix hints that a cost trade-off exists but never tells the agent how to weigh it.

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