Skip to main content
Glama

SouthPow crypto & market data

buy_coin_KERNEL

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

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

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 a solid job: it discloses the cost ($0.01 USDC on Base), the payment rail, that no account or API key is needed, that failed calls are not charged, and the upstream sources (Coinbase Exchange with Kraken cross-check). It stops short of describing response format, latency, rate limits, or freshness guarantees.

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 a tight, front-loaded block: 'Paid.' first (the most decision-relevant fact), then the data delivered, then cost/access, then the endpoint URL. The telegraphic fragment style is efficient, though the stacked clauses make it slightly denser than necessary.

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?

With no output schema and no parameters, the description must convey both the payload and the commercial terms, and it covers the returned fields, the price, the payment chain, and failure billing. It omits response format (JSON), timestamp/currency conventions, and any reliability or rate-limit context, which keeps it from a 5.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly requires no arguments, consistent with the empty schema.

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 (KERNEL/USD) and enumerates what is returned: last price, 24h open/high/low, % change, 24h and 30d volume, plus the data sources. That is a specific, unambiguous purpose. It does not, however, differentiate itself from the generic sibling buy_crypto_price or explain why an agent would pick this symbol-specific tool over that one.

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 implied by the content (look up a live KERNEL price), and the paid/access conditions hint at when it is appropriate. There is no explicit guidance on when to use this instead of buy_crypto_price or the other price-related siblings, and no statement of exclusions or prerequisites beyond 'no account, no API key'.

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