Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ADO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 real work: it discloses the paid nature, the exact price and payment rails, that no account or API key is needed, that failed calls are not charged, and the endpoint URL. The main gap is the absence of any latency, idempotency or retry/duplicate-charge guidance, which matters for a paid call.

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?

The description is front-loaded with 'Paid.' and packs cost, coverage, auth and endpoint into a few short clauses with no filler. The telegraphic style leaves the final clause ('URL https://...') slightly bare, but nothing is wasted.

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 and no annotations, the description supplies the fields returned, the access requirements, the payment terms and the endpoint, which is close to everything needed to call it correctly. The only meaningful omission is disambiguation from the overlapping buy_coin_ADO and buy_crypto_price siblings.

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 no schema semantics for the description to add. The baseline is a 4, and the description correctly spends no words on arguments, instead covering cost and access.

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 a specific resource and payload: 'ADO Protocol (ADO) price: live USD price, 24h change and market-cap rank.' An agent can immediately tell this is a single-asset price lookup rather than an audit, TVL or yields tool. It does not, however, distinguish itself from the near-identical sibling 'buy_coin_ADO' or from 'buy_crypto_price', so the differentiation is only partial.

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 context is implied by the commercial framing ('Paid ... $0.05 USDC on Base or Solana'), which tells the agent a purchase is involved, but there is no explicit when-to-use or when-not-to-use statement. Nothing says why one would call this instead of the sibling buy_coin_ADO that appears to cover the same asset, leaving the agent to guess.

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