Skip to main content
Glama

SouthPow crypto & market data

buy_coin_DEXT

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

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

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, the exact price and settlement chain/token, that no auth is required, and that failed calls are not charged — the last point is a meaningful policy an agent could not infer. It omits freshness/latency and response shape.

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?

Dense and front-loaded — payment status first, then the data covered, then cost, then auth policy, then endpoint. The telegraphic style ('Paid.', 'DEXT/USD live:') is efficient though slightly fragmented; every clause carries information.

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?

No output schema and no annotations exist, so the description must describe the payload, and it does enumerate the returned fields and sources. For a fixed, parameterless price endpoint that is nearly sufficient; only the concrete response format and data freshness are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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, but the description adds nothing about invoking it beyond a raw URL; there is no note on whether the URL is informational or the actual transport, which slightly undercuts the otherwise clean zero-param design.

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 the specific resource (DEXT/USD) and enumerates the exact data returned: last price, 24h OHLC, % change, 24h and 30d volume, plus the upstream venues. Among hundreds of near-identical buy_coin_* siblings, the ticker in the first line is what tells an agent this is the DEXT snapshot.

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 implied by the cost note ('$0.10 USDC on Base') and by naming the asset, but there is no explicit guidance on when to prefer this over a general price sibling such as buy_crypto_price, nor any exclusions or prerequisites beyond 'no account, no API key'.

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