Skip to main content
Glama

SouthPow crypto & market data

buy_tok_NOCK

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

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

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 disclosure burden and does well: it states the tool is paid, the exact cost ($0.01 USDC), the accepted payment networks (Base, Solana), that no auth is needed, and that failed calls are not charged — the last being an important billing-safety fact an agent cannot infer. It omits rate limits, price freshness/caching, and response shape, which keeps it from 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?

Six short clauses, front-loaded with the payment flag ('Paid.') and then the purpose, so cost is visible before an agent commits. Every clause is factual and none is filler, though the bare fragments read as telegraphic rather than structured.

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-param, no-output-schema price tool, the definition covers what is returned (price, 24h change, market-cap rank), what it costs, how to pay, and that failures are free. The remaining gap is freshness/latency of the quoted price, which matters for an agent reasoning about 'live' data.

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 does not invent parameters and instead documents cost and access, which is the useful non-schema information 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: 'Nockchain (NOCK) price: live USD price, 24h change and market-cap rank.' That is enough for an agent to tell this apart from the hundreds of sibling buy_tok_*/buy_coin_* tools. It stops short of 5 because it never contrasts itself with the generic buy_crypto_price endpoint that could also serve a price lookup.

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 'call this to get NOCK price.' There is no explicit statement of when to prefer this over buy_crypto_price or the buy_coin_NOCK sibling, and no exclusions. The prerequisites it does list ('no account, no API key', payment rails) are access conditions rather than routing 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