Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SKL

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 real job: it discloses the price ($0.05 USDC on Base), the payment rail, that no account or API key is needed, and that failed calls are not charged. It also names the upstream data sources (Coinbase Exchange with a Kraken cross-check), which materially informs trust in the numbers. It stops short of describing rate limits, latency, or what the success response body looks like.

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?

Extremely dense and front-loaded: payment status first, payload second, cost/auth/failure policy third, endpoint last. No padding sentences. The telegraphic style ('Paid.', dangling colon clauses) is slightly clipped but never ambiguous.

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 paid lookup with no output schema and no annotations, the description covers the three things an agent actually needs: what data comes back, what it costs, and what happens on failure. Only the response envelope/shape is left unstated, which is a minor residual gap given there is no output schema.

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 to disambiguate; baseline 4 applies. The description correctly implies the invocation is a bare GET against a fixed URL with no arguments needed.

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 (SKL/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. It is a data-retrieval spec rather than a verb phrase, but an agent can tell it is a market-data lookup for one specific ticker. It does not explicitly contrast itself with siblings like buy_crypto_price or the other buy_coin_* variants.

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 payload description and the cost note, but there is no explicit 'use this when...' or 'prefer buy_crypto_price for...' guidance. In a namespace of 300+ near-identical buy_coin_* tools, the absence of any routing advice leaves the agent to infer that ticker identity is the sole selection criterion.

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