Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LUNC

Paid. Terra Luna Classic (LUNC) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/LUNC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — the key risk facts for an agent deciding to spend money. It omits rate limits, latency, and whether the price is real-time versus cached, 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?

Three short sentences with the cost signal ('Paid.') front-loaded, followed by payload contents and then payment/auth terms. Every clause earns its place; there is no repetition of the tool name and no 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, no-output-schema tool with no annotations, the definition covers what an agent needs: what data comes back, what it costs, how to pay, that no credentials are required, and the failure-charge policy. The remaining gap is return-shape detail (field names, timestamp/freshness of the quote), which matters because no output schema exists to fill it in.

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 semantics to explain and the baseline of 4 applies. The description correctly implies the coin is fixed by the endpoint rather than selectable, which is consistent with the empty input schema.

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 the specific resource (Terra Luna Classic / LUNC) and enumerates the exact data points returned: live USD price, 24h change, and market-cap rank. That is far more specific than the ticker-only name. It stops short of a 5 because it never differentiates itself from the many near-identical siblings (buy_coin_LUNC-style entries, buy_crypto_price, buy_tok_LUNA), leaving the agent to infer the distinction from the naming convention alone.

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 only implied: an agent can infer this is the LUNC spot-price lookup, and the payment preamble establishes the cost and rails. There is no explicit statement of when to prefer this over buy_crypto_price or the buy_coin_* family, nor any exclusion of cases where it should not be called.

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