Skip to main content
Glama

SouthPow crypto & market data

buy_coin_KNC

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

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

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 supplied, the description carries the full burden and does real work: it discloses the price ($0.002 USDC on Base), the payment rail, that no account or API key is needed, and that failed calls are not charged. That is exactly the kind of commercial and auth context annotations would otherwise supply. It stops short of saying how payment is attached, whether there are rate limits, or latency/refresh expectations.

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?

Dense, front-loaded and largely waste-free: it leads with the paid flag, then the payload, then pricing and access terms, then the endpoint. The one weak spot is the bare 'Paid.' opener and the raw URL, which read like copied billing copy rather than agent-facing structure. Still, every clause carries information.

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 tool, the description covers the important gaps: it lists the returned fields, names the data sources, and states the cost and access model. Missing is what a response envelope looks like (units, timestamp, JSON shape) and any reliability/pagination caveats, but the field enumeration goes most of the way.

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 no parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misdescribes or invents inputs.

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?

Names the specific resource (KNC/USD) and enumerates exactly what data comes back: last price, 24h open/high/low, % change, 24h and 30d volume, plus the underlying venues (Coinbase Exchange with Kraken cross-check). That is far more specific than the sibling buy_coin_* names, which are differentiated only by ticker. It does not point at the generic sibling buy_crypto_price, so the boundary between this and the multi-asset tool is left implicit.

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 infers this is the KNC-specific spot/market-data call from the ticker in the name and the data fields listed. There is no explicit statement of when to prefer this over buy_crypto_price or how it relates to the other per-coin tools. The prerequisite-style facts (no account, no API key, pay-per-call) are useful context but are 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