Skip to main content
Glama

SouthPow crypto & market data

buy_coin_KARRAT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the full behavioral burden and does well: it discloses that the call is paid, the exact price and payment rail, that no authentication is required, and that failed calls are not charged. It omits return shape/latency and whether quotes are delayed, which keeps it short of a 5.

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?

Front-loads 'Paid.' so the cost signal is the first thing an agent reads, then packs dataset contents, pricing, access requirements, and billing policy into a few dense clauses. The endpoint URL is the only arguably extraneous element, and it is useful for verification.

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 read tool with no output schema, the description enumerates the returned fields, names data sources, and covers payment and auth prerequisites — enough for correct invocation. Minor gaps remain around response format and freshness/delay of the quote.

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; baseline 4 applies. The description correctly implies the call is fully self-contained via the embedded endpoint URL.

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?

States a specific resource and dataset: KARRAT/USD live price plus 24h open/high/low, % change, and 24h/30d volume, with named sources (Coinbase Exchange, Kraken cross-check). The ticker in the text and name separates it from the many buy_coin_* siblings, but the description never explicitly says it is the KARRAT-only variant or points to alternatives like buy_crypto_price.

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 establishes conditions of use (paid, $0.10 USDC on Base, no account or API key, failed calls not charged), which is genuinely useful gating information. However, there is no explicit when-to-use versus sibling guidance — nothing tells the agent to prefer this over the generic buy_crypto_price or explains when the 30d volume cross-check matters.

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