Skip to main content
Glama

SouthPow crypto & market data

buy_coin_NKN

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

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

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 substantial work: it declares the call is paid, the exact price ($0.002 USDC on Base), that no account or API key is needed, that failed calls are not charged, and which exchanges the data comes from. That is unusually rich disclosure for cost, auth, and billing-on-failure. It omits rate limits, latency, and whether payment is handled automatically by the client, which keeps it below 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 a single dense block of fragments, front-loaded with 'Paid.' and the dataset scope, so the most decision-relevant facts come first. Every clause carries information (fields, sources, price, auth, refund policy, endpoint), though the telegraphic style makes it read more like a spec line 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, no-output-schema tool the description covers what is returned (enumerated fields), where it comes from, what it costs, and how billing on failure works — enough for an agent to call it correctly. Gaps are secondary: response encoding and how the USDC payment is actually settled are not explained.

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 and there is nothing for the description to disambiguate. The description correctly adds no parameter discussion, instead using the space for scope and cost information.

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 dataset: NKN/USD last price, 24h open/high/low, percent change, and 24h/30d volume, with named sources (Coinbase Exchange, Kraken cross-check). An agent can tell exactly what it gets, and the token-specific name separates it from the ~400 sibling buy_coin_* feeds. It stops short of 5 because the tool name says 'buy_coin' while the description describes a price-data purchase, leaving a slight ambiguity about whether a coin or a data call is being bought.

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 rather than stated: an agent infers this is the NKN-specific price feed and that the generic buy_crypto_price sibling exists, but the description never says when to prefer one over the other or what to do for other tokens. The 'No account, no API key' line hints at accessibility prerequisites but is not framed as 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