Skip to main content
Glama

SouthPow crypto & market data

buy_tok_KAG

Paid. Kinesis Silver (KAG) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/KAG.

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

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 well: it discloses the cost ($0.05 USDC), the two accepted payment chains (Base or Solana), that no account or API key is needed, that failed calls are free, and the underlying endpoint URL. The main gap is that it says nothing about rate limits, latency, or what a failure response looks like.

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?

Five short sentences, no filler, opening with "Paid." so the cost characteristic is front-loaded before the agent commits. The payload description, pricing, auth preconditions and endpoint each appear exactly once.

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, single-asset price call this covers what an agent needs: what comes back, what it costs, which chains pay for it, and that no credentials are required. Missing only edge-case behavior (rate limits, staleness of the price, error shape), which keeps it just short of complete.

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 is 4. The mention of two payment rails (Base or Solana) is a call-time detail handled outside the input schema, which slightly enriches the picture without being strictly required.

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 a specific resource and data payload: Kinesis Silver (KAG) live USD price, 24h change and market-cap rank, with the ticker in both the tool name and the text. An agent can tell what it returns without opening the schema. It does not, however, distinguish itself from the many adjacent price tools in the sibling list (buy_coin_*, buy_crypto_price), leaving asset-selection to the name alone.

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?

"Paid... No account, no API key. Failed calls not charged" gives useful preconditions for calling it, but there is no statement of when to prefer this over buy_coin_KAG or buy_crypto_price, which appear to cover overlapping ground. Usage is implied by the asset ticker rather than explained.

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