Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LUCIC

Paid. Lucidum (LUCIC) 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/LUCIC.

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

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, the description carries the full burden, and it does well: it discloses the $0.01 USDC cost, the accepted payment chains (Base or Solana), the lack of auth requirements, and importantly that failed calls are not charged. The one gap is that it doesn't say whether calls are idempotent or how payment is settled.

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?

It's dense and front-loaded: 'Paid' first, then what you get, then price, then access terms, then the endpoint. Every clause carries information. Slightly telegraphic, and the raw URL sits a bit awkwardly at the end, 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?

With no output schema, the description must convey the return payload, and it does by listing the three fields returned. For a zero-parameter, single-resource paid lookup this is essentially complete; only the response format (JSON shape) is left unspecified.

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 input parameters, so there is nothing in the schema for the description to elaborate on. Baseline 4 applies; the description doesn't need to explain parameters because none 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 a specific resource (Lucidum/LUCIC price) and enumerates the exact fields returned: live USD price, 24h change, and market-cap rank. It's clear what the tool does, though it doesn't explain how it differs from the many sibling buy_tok_* or buy_crypto_price endpoints beyond the ticker itself.

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: 'Paid' plus the token name suggests it's the LUCIC-specific price lookup, and 'No account, no API key' tells the agent it can call it freely. There is no explicit when-to-use statement or routing to alternatives like buy_crypto_price for a multi-coin quote.

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