Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SD

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 burden and does a solid job: it discloses the commercial model, the price and payment chain, the absence of authentication, and the billing policy on failures. It does not cover rate limits, data latency/staleness, or the shape of the response body, which leaves some behavioral gaps for a paid endpoint.

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?

The text is telegraphic and front-loaded, leading with the paid flag and the data payload before terms. Every clause carries information, though the literal endpoint URL is redundant for a zero-parameter MCP call and the fragment style borders on cryptic in places.

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 annotations, the description compensates by listing the returned metrics and their sources, plus payment and failure-billing behavior. It stops short of describing units, timestamps, or response structure, which an agent would still need to interpret results confidently.

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 nothing for the description to disambiguate beyond confirming the ticker is baked into the tool. Baseline 4 applies for a parameterless tool; the description correctly implies no arguments are needed by fully specifying the call in the text.

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 states the exact resource (SD/USD live price) and enumerates the returned fields: last price, 24h open/high/low, percent change, 24h and 30d volume. It also names the underlying venues (Coinbase Exchange with Kraken cross-check), which distinguishes it from the hundreds of ticker siblings whose identity is only implied by the tool name. An agent can tell immediately what data this yields.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Preconditions for use are explicit: it is paid, costs $0.002 USDC on Base, needs no account or API key, and failed calls are not charged. What is missing is any routing guidance versus the generic sibling (buy_crypto_price) or a statement of when not to call it, e.g. when free price sources suffice.

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