Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LUMIA

Paid. Lumia (LUMIA) 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/LUMIA.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the full behavioral burden and does a decent job: it discloses that the call is paid ($0.05 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged. It stops short of describing the response shape or whether the given URL is a direct endpoint the agent may call itself.

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?

Front-loaded with what the agent gets (price, 24h change, rank), then cost, then auth, then failure policy — a sensible priority order. The telegraphic fragments are slightly choppy but no sentence is wasted; the trailing URL earns its place as the actual endpoint.

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-annotation, no-output-schema tool, the description covers the key unknowns: price, payment method and amount, absence of authentication, and failure billing. Only the return format and the semantics of the embedded URL remain ambiguous.

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 to document and the baseline of 4 applies. The description does at least communicate that no request arguments or credentials are needed.

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?

States a concrete verb+resource: it returns live USD price, 24h change and market-cap rank for Lumia (LUMIA). That is specific enough that an agent knows what data comes back. It does not, however, distinguish itself from the very similar sibling buy_coin_LUMIA (or buy_crypto_price), which appears to cover overlapping ground.

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: buy this when you need LUMIA market data. There is no statement of when to prefer it over the closely-named alternative buy_coin_LUMIA or over the generic buy_crypto_price sibling, and no exclusions are given, which is a real gap given the hundreds of sibling tools covering the same coin.

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