Skip to main content
Glama

SouthPow crypto & market data

buy_coin_WELL

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

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

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 delivers: paywall model and price ($0.01 USDC on Base), no account or API key required, failed calls are not charged, dual data sources (Coinbase Exchange with Kraken cross-check), and the endpoint URL. It omits rate limits, data staleness/latency, and response format, keeping it short of 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.

Conciseness5/5

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

Five dense clauses, zero filler: paid status first, then the data fields, then price/chain, auth requirements, billing policy, and URL. Every sentence carries decision-relevant information for the agent.

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?

For a zero-parameter tool with no output schema, the description usefully enumerates the return fields and the payment/auth model, which is close to complete. Only edge details — whether data is real-time or delayed, and response shape — are left unspecified.

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 compensate for; the baseline for 0 params applies. The description correctly adds no parameter guidance, which is right for a parameterless endpoint.

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?

The description names the exact resource (WELL/USD live price) and enumerates the specific fields returned: last price, 24h open/high/low, % change, and 24h/30d volume. Combined with the ticker in the tool name, an agent can tell this apart from the hundreds of sibling buy_coin_<TICKER> 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?

"Paid" and the $0.01 USDC price imply this is the paid alternative to free siblings such as buy_crypto_price, but the description never explicitly states when to use this versus those alternatives or when not to use it. Usage is only implied through the cost signal.

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