Skip to main content
Glama

SouthPow crypto & market data

buy_coin_NEX

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

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

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 burden and does unusually well: it discloses that calls are paid ($0.25 USDC on Base), that no account or API key is needed, that failed calls are not charged, and the exact endpoint URL and upstream data sources. It omits latency, rate limits, data freshness/delay, and the response shape, which are the remaining behavioral gaps for a paid data call.

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?

Every element earns its place: cost, auth model, billing policy, data fields, sources, and URL, with the payment fact front-loaded as 'Paid.' The telegraphic fragment style ('Paid.', bare colon-list) is dense but readable and avoids any filler.

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 tool with no output schema, the description must describe return content, and it enumerates the fields and source venues adequately. What is missing is the response format (JSON shape, units, timestamp field) and freshness guarantees, which matter for a paid quote call. Overall it is close to complete for this tool's complexity.

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 meaning to add and the baseline of 4 applies. The description correctly implies a parameterless fixed-asset lookup rather than leaving an agent hunting 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 dataset: live NEX/USD price with last, 24h OHLC, % change, and 24h/30d volume, plus the source venues (Coinbase Exchange, Kraken cross-check). The asset-specific name and explicit data list separate it from the hundreds of sibling buy_coin_* variants. It never states the verb ('returns quote data') and never says it is the NEX member of a per-asset family, so differentiation is inferred from the name rather than spelled out.

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 only: an agent can infer this is the endpoint for NEX price data. There is no explicit when-to-use or when-not guidance, and nothing addresses the potentially overlapping generic sibling buy_crypto_price, so an agent has no stated rule for choosing between them. The payment precondition is stated, which is a partial usage constraint.

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