Skip to main content
Glama

SouthPow crypto & market data

buy_coin_KTA

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 does it well for a paid tool: it discloses the price ($0.10 USDC on Base), the payment chain, that no account or API key is needed, that failed calls are not charged, and the data provenance and endpoint URL. What is missing is rate-limit behavior, latency expectations, and what a partial failure (e.g. Kraken unavailable) does to the response.

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?

A single dense sentence block with the cost signalled first and the returned fields enumerated compactly; no filler or redundancy. Every clause (price, payment, auth-free, no-charge-on-failure, URL) adds a distinct fact an agent would want before calling.

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 input parameters, no output schema and no annotations, the description supplies what is missing: a field-level list of return values plus the commercial and auth conditions. It falls short of a full picture because the shape of the response (JSON keys, units, timestamp granularity) is only named, not described, which matters when no output schema exists.

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 meaning to convey and the baseline of 4 applies. Nothing in the description conflicts with the empty input 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 the specific resource and the exact data returned: KTA/USD last price, 24h open/high/low, percent change, 24h and 30d volume. An agent can distinguish it from the hundreds of sibling buy_coin_* tools by the KTA symbol and data set. It loses a point because there is no explicit action verb (fetch/returns) and the tool name's 'buy' framing is never reconciled with what is actually a read-only price lookup.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives such as buy_crypto_price or buy_coin_* for other symbols, and no mention of prerequisites or exclusions. Usage is only inferable from the symbol and the returned fields. The 'Coinbase Exchange, Kraken cross-check' note hints at source quality but gives no selection guidance.

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