Skip to main content
Glama

SouthPow crypto & market data

buy_coin_NCT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the burden and does so well beyond the minimum: it discloses that the call is paid ($0.002 USDC on Base), the settlement currency and chain, that no account or API key is required, that failed calls are not charged, and the upstream data sources including a Kraken cross-check. Missing only rate limits or latency/retry behavior to reach 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the billing flag ('Paid.') before the payload description, then cost, then payment mechanics. Telegraphic but every clause carries distinct information; no repetition of the tool name.

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?

There is no output schema and no annotations, yet the description enumerates the returned metrics and the data provenance, which is the main thing an agent needs. For a zero-parameter, fixed-endpoint price tool, only return formatting (units, timestamp field) is left unspecified.

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 schema meaning to add; baseline 4 applies. The description correctly implies the asset is fixed by the endpoint rather than parameterized, so an agent will not look for a symbol argument.

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 verb-equivalent (live NCT/USD price) and enumerates exactly which fields come back: last price, 24h open/high/low, % change, 24h and 30d volume. It is not differentiated from siblings in prose, but the ticker in the tool name plus the explicit pair (NCT/USD) makes the target asset unambiguous among the buy_coin_* family.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to choose this over alternatives such as buy_crypto_price or other price sources, and no exclusions or prerequisites beyond 'No account, no API key'. The agent must infer usage purely from the asset pair, which is adequate for a same-shaped family but is not real 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