Skip to main content
Glama

SouthPow crypto & market data

buy_tok_DODO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 that the call is paid, the exact cost ($0.01 USDC), accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. That failure/charging policy is exactly the kind of behavioral detail an agent needs before spending money. It stops short of describing the response shape, which matters since no output schema exists.

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?

It is front-loaded with 'Paid.' followed immediately by the payload and then the commercial terms, so the cost signal arrives before the agent commits. Every clause carries information, though the raw endpoint URL is arguably redundant with the tool's own invocation metadata and the telegraphic style borders on terse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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, no-annotation tool, the description covers what is returned and what it costs, which is most of the picture. The gap is the payment mechanism: it says the call costs $0.01 USDC on Base or Solana but never explains how an agent actually settles that payment, which is essential for a tool whose primary risk is spending money.

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 and the baseline of 4 applies. The description does not waste words inventing parameter semantics that do not exist.

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 names the specific resource (DODO token) and the exact payload: live USD price, 24h change, and market-cap rank. That is a concrete verb+resource statement an agent can act on. It does not, however, distinguish itself from the very similar siblings buy_coin_DODO and buy_crypto_price, which appear to cover overlapping price data.

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 can infer 'call this to get DODO's price.' The description never states when to prefer this over buy_coin_DODO or buy_crypto_price, nor does it give any when-not conditions. The purchase mechanics ('Paid', '$0.01 USDC') are present but that is cost guidance, not selection guidance.

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