Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LUNA

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

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

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 at all, the description carries the full behavioral burden and does a credible job: it discloses the cost, the accepted payment chains, that no account or API key is required, that failed calls are not charged, and the underlying endpoint URL. It stops short of stating rate limits, latency, or response shape beyond the three named fields.

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?

The description is short, front-loaded with the data noun phrase, and each clause (cost, chains, auth, failure billing, URL) carries distinct decision-relevant information. The raw URL is marginal padding but is the only slightly unnecessary element.

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 paid call, the description supplies the essentials an agent needs: what data comes back, what it costs, how payment works, and that failures are free. Missing details are minor (exact response structure, freshness/latency, refresh cadence).

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 the description could clarify beyond what the empty schema already implies. The baseline of 4 applies; the description correctly avoids inventing parameter discussion that does not exist.

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 exact resource (Terra/LUNA) and the exact payload (live USD price, 24h change, market-cap rank), which is far more specific than the bare tool name buy_tok_LUNA reveals. It does not, however, distinguish this paid per-token endpoint from the many analogous siblings such as buy_coin_* price tools or buy_crypto_price, leaving the agent to infer the difference.

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: an agent can infer 'call this when you need a LUNA spot quote.' The payment details ($0.01 USDC on Base or Solana, no account, failed calls not charged) indirectly inform a cost/selection decision, but nothing says when to prefer this over buy_crypto_price or the buy_coin_* family, and no prerequisites beyond payment are spelled out.

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