Skip to main content
Glama

SouthPow crypto & market data

buy_coin_NOM

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 cost and payment rail ($0.10 USDC on Base), that no account or API key is needed, and that failed calls are not charged - the key economic behavior for a paid tool. It stops short of stating latency, data freshness/delay, caching, or rate limits, which matter for a live price feed.

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?

Cost and paid status are front-loaded in a single word, followed by the data payload, then the commercial terms. The telegraphic style ('24h open/high/low', '% change') is dense but readable, and every clause adds information; only the raw URL feels slightly out of place.

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 annotations, the description compensates by enumerating the returned fields and the payment/failure terms, which is close to a full contract for a zero-parameter tool. It would be stronger if it stated the response format (JSON) and whether the quoted price is real-time or delayed.

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. It correctly does not invent any inputs and instead spends its words on the endpoint URL and returned data.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (NOM/USD live price) and enumerates exactly which fields come back: last price, 24h open/high/low, % change, 24h and 30d volume. Because each sibling is a per-asset variant named by ticker, naming NOM and its data sources (Coinbase Exchange with Kraken cross-check) is enough to distinguish it from the other buy_coin_* tools.

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?

Prerequisites are clear (paid, $0.10 USDC on Base, no account or API key, failed calls not billed), which lets an agent decide whether it can afford to call. However, it never states when to prefer this over the generic buy_crypto_price sibling or what to do if the payment cannot be made, so the usage routing is only implied.

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