Skip to main content
Glama

SouthPow crypto & market data

buy_coin_LQTY

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

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

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 supplied, the description carries the full burden and does well: it discloses that the call is paid ($0.25 USDC on Base), requires no account or API key, is not charged on failure, and that data comes from Coinbase Exchange with a Kraken cross-check. Missing are the payment mechanism (how the USDC is actually remitted), latency, rate limits, and freshness of the quote.

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?

Extremely dense and front-loaded: 'Paid.' leads, followed by data fields, price, auth terms, and endpoint. Every clause carries information. The staccato fragments and raw URL make it slightly telegraphic but nothing is wasted.

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 the return payload, and it does so field by field, plus cost, auth, and failure policy. The notable gap is how an agent actually executes the $0.25 USDC payment, which is left implicit.

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 nothing for the description to disambiguate and the baseline applies. The description correctly spends no words on inputs and instead invests them in outputs and payment terms.

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 (LQTY/USD live price) and enumerates exactly what comes back: last price, 24h open/high/low, % change, 24h and 30d volume. It is distinguishable from the hundreds of buy_coin_<TICKER> siblings because the ticker is in both name and description. The only wrinkle is that the tool name says 'buy_coin' while the description describes a paid price lookup, so the verb must be inferred.

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 by the ticker and the pricing model rather than stated: an agent can infer 'call this when you need LQTY/USD data and are willing to pay $0.25'. There is no explicit routing versus alternatives such as buy_crypto_price or other buy_coin_* tools, and no statement of when not to use it.

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