Skip to main content
Glama

SouthPow crypto & market data

buy_coin_QNT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 substantial work: it discloses the paid model ($0.002 USDC on Base), that no account or API key is needed, that failed calls are not charged, and that data comes from Coinbase Exchange with a Kraken cross-check. Gaps remain around rate limits, latency, and what an error response looks like, 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.

Conciseness5/5

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

Every clause earns its place: cost, data fields, provenance, payment rail, auth model, billing-on-failure, and endpoint URL, all front-loaded with the price data before the commercial terms. No filler or redundancy.

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 their sources, which is close to a return-value spec. It stops short of describing the response structure or error shape, but for a zero-parameter single-endpoint feed this is nearly complete.

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; there is no parameter meaning the description could add or omit. The description correctly signals the parameterless nature by naming the fixed asset pair in the text itself.

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?

The description names the exact resource and scope — 'QNT/USD live' with last price, 24h OHLC, % change, and 24h/30d volume — so an agent can tell precisely what this tool returns. Against ~300 siblings that differ only by ticker suffix, naming the pair 'QNT/USD' is exactly the disambiguating information needed.

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: the agent can infer this is the QNT-specific price feed and that payment is required, but the description never says when to prefer it over a general sibling like buy_crypto_price, nor what happens if a non-QNT asset is wanted. No explicit when/when-not guidance is given.

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