Skip to main content
Glama

SouthPow crypto & market data

buy_coin_KSM

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

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

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 well: it discloses that the call is paid, the exact price and settlement chain, that no account or API key is needed, that failed calls are not charged, and which exchanges the data comes from. Remaining gaps are the payment mechanics themselves and any latency/freshness guarantees.

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: 'Paid.' leads, then the data fields, then cost/auth terms, then the URL. Every clause carries information. The telegraphic style ('Paid.', bare abbreviations like '30d volume') is efficient but slightly clipped.

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, no-annotation, no-output-schema tool, the description covers purpose, returned fields, data provenance, pricing, auth requirements, and failure billing. What is missing is the response envelope shape and how payment is actually transacted, but nothing essential to a correct first call is absent.

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 schema has zero parameters, so the baseline is 4 and there is nothing further the description could reasonably add on this dimension. It also usefully pre-describes the payload fields it returns, which compensates for the absence of an output schema.

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 and verb-equivalent ('KSM/USD live: last price, 24h open/high/low, % change, 24h and 30d volume'), so an agent knows exactly what data comes back. Sibling differentiation is carried mostly by the symbol in the tool name rather than the text, and it does not contrast with buy_crypto_price, which keeps it from a 5.

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 only implied: an agent infers 'call this to get KSM spot data'. The commercial terms ('Paid', '$0.05 USDC on Base', 'No account, no API key') help it judge cost and prerequisites, but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as buy_crypto_price or the other buy_coin_* variants.

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