Skip to main content
Glama

SouthPow crypto & market data

buy_coin_WMTX

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

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

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 substantial work: it discloses the paid model ($0.05 USDC on Base), that no account or API key is required, that failed calls are not charged, and that data comes from Coinbase Exchange with a Kraken cross-check. Missing are retry/error semantics and freshness guarantees, which keeps it below a 5.

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 dense and front-loaded: data scope first, then cost, then access requirements, then the endpoint URL. The telegraphic style ('Paid.', an unlabeled URL) is efficient but slightly clipped; every clause still 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?

Because there is no output schema, the description correctly enumerates the returned fields and their sources, which is what an agent needs to judge fitness. It does not describe the response envelope or failure modes beyond the no-charge promise, which is a modest gap for a paid data endpoint.

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 there is nothing for the description to clarify and the schema is trivially complete. The description adds no parameter meaning beyond naming the quoted pair, which is consistent with the baseline for a 0-param tool.

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 scope: WMTX/USD live price plus a concrete field list (last price, 24h open/high/low, % change, 24h and 30d volume). That is enough to separate it from the hundreds of sibling buy_coin_* tickers, though the leading fragment 'Paid.' rather than a verb like 'Fetch' makes the action slightly implicit.

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 ticker in the name and the 'WMTX/USD live' phrasing, and the cost/no-account notes help an agent decide it is viable. There is no explicit statement of when to prefer this over a sibling like buy_crypto_price or another ticker tool, and no when-not 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