Skip to main content
Glama

SouthPow crypto & market data

buy_coin_KMNO

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

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

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, the description carries the full behavioral burden and does well: it discloses the pay-per-call cost and currency, the chain (Base), that no account or API key is needed, that failed calls are free, and the upstream data sources (Coinbase Exchange with Kraken cross-check). Missing only freshness/latency and rate-limit behavior.

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?

Terse and front-loaded: cost first, then payload, then payment terms, then endpoint. Every clause carries information, though the telegraphic 'Paid.' opener is slightly cryptic and the dense parenthetical requires a second read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter paid HTTP endpoint with no output schema, the description enumerates the returned fields, states the price and payment mechanics, confirms no auth is required, and even gives the URL. An agent has everything needed to call it and anticipate the result.

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 and the baseline of 4 applies. The description correctly implies a fixed, ticker-scoped request via the 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 concrete resource and payload: 'KMNO/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', so an agent knows exactly what comes back. It does not explicitly route to the generic sibling (buy_crypto_price) or the other ticker tools, relying on the ticker in the name for differentiation.

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?

The description surfaces the condition that matters for a paid tool ('Paid', '$0.25 USDC on Base', 'Failed calls not charged'), which helps an agent decide whether to spend. It never states when to prefer this over buy_crypto_price or the neighboring buy_coin_<TICKER> tools, so selection guidance remains implied by the ticker symbol alone.

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