Skip to main content
Glama

SouthPow crypto & market data

buy_coin_KITE

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

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

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 supplied, the description carries the full behavioral burden and does substantial work: it discloses that calls are paid ($0.10 USDC on Base), that no account or API key is needed, that failed calls are not charged, and that data is sourced from Coinbase Exchange with a Kraken cross-check. What it omits is rate limiting, response format/shape, and freshness or latency expectations.

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?

Four tight sentences, front-loaded with the highest-value signal ('Paid.'), then scope, then payment/auth terms, then the endpoint URL. Every clause carries distinct information and nothing is repeated from structured fields.

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-output-schema price lookup, the description covers what the agent needs to decide and pay: data fields, sources, price, chain, auth model, and billing on failure. It stops short on return presentation (JSON shape, units, timestamp semantics) and rate limits, which are the remaining unknowns an agent would want.

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 is 4; there is no parameter meaning for the description to add. The schema is an empty object with 100% coverage, so no compensation is needed.

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 exact resource (KITE/USD) and enumerates the returned data points (last price, 24h open/high/low, % change, 24h and 30d volume), which distinguishes it from the ~300 sibling buy_coin_<SYMBOL> tools by ticker. It lacks an explicit verb — 'KITE/USD live:' is elliptical — and it never resolves the tension with the 'buy_coin' name, so an agent must infer this is a data retrieval endpoint rather than a purchase action.

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 can infer it should call this to get KITE price data. There is no guidance on when to prefer this over the sibling buy_crypto_price aggregator, no statement about staleness or freshness guarantees, and no 'when not to use' clause. Cost and payment info is present but that is procurement detail, not 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