Skip to main content
Glama

SouthPow crypto & market data

buy_coin_WET

Paid. WET/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/WET.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 unusually well: it discloses that the call is paid ($0.05 USDC on Base), that no account or API key is required, that failed calls are not charged, the upstream data sources (Coinbase Exchange with Kraken cross-check), and the endpoint URL. It stops short of describing response shape or data latency/freshness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the billing fact ('Paid.') then immediately names the pair and the returned fields, followed by cost, auth posture, refund policy, and URL. Dense but every fragment earns its place, with no filler sentences.

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?

With no output schema and no parameters, the description compensates by enumerating the returned data fields and the source venues, which is what an agent needs to decide relevance. It could be slightly more complete by stating the response format or quote freshness, but nothing essential to invoking it is 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 there is no parameter semantics to explain; the baseline for a 0-param tool applies. The description correctly implies no inputs are needed by noting no account or API key is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (WET/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. The ticker in the name plus the explicit pair makes it trivially distinguishable from the hundreds of sibling buy_coin_<TICKER> tools.

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?

Gives purchase context (cost, payment rail, no account/API key, failed calls not charged) which is enough to know how to transact, but never says when to choose this over the generic buy_crypto_price sibling or what the alternative is for multi-asset quotes. Usage is implied by the ticker, not stated.

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