Skip to main content
Glama

SouthPow crypto & market data

buy_tok_WKC

Paid. Wiki Cat (WKC) 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/WKC.

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

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 burden and does well: it discloses the price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. It stops short of stating rate limits, data freshness/latency, or whether the result is cached, which keeps it off 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is dense and front-loaded – asset and payload first, then cost and payment mechanics, then the endpoint URL. The telegraphic phrasing ('Paid.', fragment clauses) is efficient rather than wasteful, though it reads more like a price tag than prose.

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 paid lookup with no output schema, the description covers the essentials: what fields come back, what it costs, which chains to pay on, and that failures are free. The remaining gap is the lack of differentiation from buy_coin_WKC and buy_crypto_price, which is the main thing an agent still has to guess.

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, which sets the baseline at 4. There are no arguments to disambiguate, so nothing further is required of the description here.

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 specific asset and the exact payload: 'Wiki Cat (WKC) price: live USD price, 24h change and market-cap rank.' That is a concrete verb+resource an agent can act on. It loses a point because the sibling set contains buy_coin_WKC and buy_crypto_price with no stated distinction between them, so an agent cannot tell from this description alone which of the three to call.

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 – the tool is for fetching WKC pricing – and the 'Paid' framing at the front does signal this is a purchasable data call. However, there is no explicit when-to-use versus when-not guidance, and no mention of the near-identical buy_coin_WKC sibling, which is a meaningful ambiguity in a catalogue this large.

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