Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SHDW

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

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

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 supplied, the description carries the full disclosure burden and does notably well: it states the cost, the payment currency and chain, that no authentication is required, that failed calls are not charged, and that data comes from Coinbase Exchange with a Kraken cross-check. What it omits is how the payment is actually transacted (wallet handshake, retry on payment failure) and the response shape, but the safety/cost profile is genuinely surfaced.

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?

Roughly four short fragments, front-loaded with "Paid." so the agent sees the cost gate before anything else. Every clause carries distinct information — data fields, sources, price, auth, failure policy, endpoint — with no filler or repetition of the name.

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?

There is no output schema, yet the description enumerates the returned fields and their provenance, so an agent knows what it gets for its $0.10. The one gap is the mechanics of paying on Base — an agent with no wallet context may not know what to do with that fact — but for a zero-parameter price lookup this is close to sufficient.

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 and the schema is empty at 100% coverage, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description correctly spends no words on phantom arguments.

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 and scope: SHDW/USD last price, 24h open/high/low, % change, and 24h/30d volume. The ticker in the name plus the explicit pair makes it trivially distinguishable from the hundreds of sibling buy_coin_* tools, each keyed to a different asset.

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?

It covers the practical preconditions for calling it ("Paid", "$0.10 USDC on Base", "No account, no API key", "Failed calls not charged"), which is real guidance an agent needs before invoking a paid endpoint. However, it never routes the agent away from alternatives such as buy_crypto_price or the other buy_coin_* siblings, so the when-to-use-this-vs-that question is left implicit.

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