Skip to main content
Glama

SouthPow crypto & market data

buy_coin_KRL

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

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

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, the description carries the full load and does well: it discloses the price ($0.01 USDC on Base), that no account or API key is required, that failed calls are not charged, and the upstream data sources. Missing behavioral details are data freshness/delay, response format, and what happens when payment or the upstream feed fails.

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?

Front-loaded with the most decision-relevant fact ('Paid'), then payload, price, access terms. Telegraphic fragments are dense but every clause carries information. Slightly staccato phrasing ('Paid. KRL/USD live: ...') costs a little readability but no sentence is wasted.

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 and no output schema, the description usefully enumerates the returned fields and their sources, which effectively substitutes for a return-value schema. Cost, auth requirements, and billing behavior on failure are all covered. Remaining gaps are data latency and response encoding, which are minor for a fixed price-snapshot endpoint.

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 the baseline of 4 applies. The description adds nothing that could be misread as a parameter, and the fixed endpoint URL reinforces that the call is parameterless.

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 concrete resource and payload: KRL/USD last price, 24h open/high/low, percent change, and 24h/30d volume, sourced from Coinbase Exchange with a Kraken cross-check. That is a specific verb-free but unambiguous data-fetch purpose. It lacks any explicit differentiation from the hundreds of sibling buy_coin_* tickers or from buy_crypto_price, leaving the agent to infer that the ticker in the name is the only difference.

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 data listed ('live' price snapshot) but there is no statement of when to prefer this over siblings such as buy_crypto_price or buy_coin_BTC, nor any when-not-to-use condition. The '$0.01 USDC on Base' opening does implicitly signal this is a paid call to be used judiciously, which is a mild routing hint. No prerequisites or alternatives are spelled out.

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