Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DIMO

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

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

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 behavioral burden and does well: it discloses that the call is paid ($0.01 USDC on Base), that no account or API key is required, and that failed calls are not charged. It also names the underlying data sources (Coinbase Exchange with a Kraken cross-check), which is meaningful provenance. The gap is that it never explains the mechanics of how payment is settled or the response format.

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 densely front-loaded: the 'Paid.' opener and the price/payment facts come before the endpoint URL, and every clause carries information. The telegraphic style ('Paid.' standing alone, the bare 'URL https://...') is slightly cryptic but wastes no words.

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 tool, the description does cover the returned fields and the cost, which is most of what an agent needs. However, the trailing URL is left unexplained — it is unclear whether the agent should call this tool (which presumably hits that endpoint) or fetch it directly — and the payment flow is not described. These are real ambiguities for a paid endpoint with no annotations or output schema to fall back on.

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 correctly implies all behavior is fixed to the DIMO/USD pair with no configurable inputs.

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 asset pair (DIMO/USD) and enumerates exactly what data it returns: last price, 24h open/high/low, percent change, and 24h/30d volume. It distinguishes itself from the many sibling buy_coin_* tools only implicitly through the ticker, since it never states that other tickers live in their own tools, but the verb-plus-resource content is unmistakable.

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 rather than stated: an agent can infer this is the way to get DIMO spot pricing, but there is no explicit when-to-use versus when-not guidance and no mention of buy_crypto_price or the sibling per-ticker tools as alternatives. The pricing and payment notes tell the agent about cost, not about selection.

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