Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DOLO

Paid. DOLO/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.002 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/DOLO.

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

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 well: it discloses the cost ($0.002 USDC on Base), payment rail, that no account or API key is needed, and that failed calls are not charged. It does not mention latency, caching/staleness of the quotes, or rate limits, which are the remaining behavioral gaps for a paid data 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?

Front-loaded with the most decision-relevant token ('Paid.'), followed by payload contents, price, access conditions, and endpoint. It is telegraphic rather than wasteful, though the fragment style ('DOLO/USD live: last price, ...') reads as a list dump rather than prose.

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?

There is no output schema, and the description compensates by enumerating the returned metrics and naming the data sources (Coinbase Exchange with Kraken cross-check). Along with the payment and refund policy, this is nearly everything an agent needs; only freshness/caching semantics are missing.

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 the baseline is 4 and there is nothing for the description to disambiguate. It correctly adds no parameter discussion, instead spending its words on cost and return fields.

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 (DOLO/USD live price) and enumerates the exact fields returned: last price, 24h open/high/low, % change, 24h and 30d volume. The coin identity lives in the tool name and is reinforced by the description, so an agent can tell it apart from the hundreds of sibling buy_coin_* tools without opening a schema.

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?

The leading 'Paid.' flag is a useful usage signal — it warns the agent this call costs money — and the price is stated up front. However, there is no explicit when-to-use guidance versus alternatives such as buy_crypto_price, and no statement of when a paid per-coin call is preferable to a broader price tool.

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