Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LUCA

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

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

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 does well: it discloses that the call is paid ($0.01 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged. These are genuinely useful behavioral facts an agent needs before spending money. It does not mention rate limits, latency, caching, or the payment flow mechanics, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the most decision-relevant fact ('Paid.') followed by purpose, cost, payment rails, and endpoint. Every sentence carries information, though 'LUCA (LUCA)' is a minor redundancy and the raw URL is arguably agent-irrelevant clutter.

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 price lookup with no output schema, the description covers what is returned, what it costs, how to pay, and that failures are free — enough for an agent to decide and invoke confidently. Only the absence of any hint about the response shape or freshness/latency keeps it from a 5.

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 the baseline is 4. Nothing in the schema needs interpretation, and the description correctly does not invent parameter detail. It adds only the endpoint URL, which is informational rather than parameter semantics.

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 specific resource (LUCA token) and the exact data returned: live USD price, 24h change, and market-cap rank. That is enough to distinguish it from the hundreds of sibling buy_tok_* tools, which differ only by token symbol. It stops short of a 5 because it never explicitly frames the tool as the LUCA-specific member of a token-price family.

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 resource name and the listed data points, but there is no explicit when-to-use or when-not guidance, and no named alternative for general or cross-token price lookups. An agent must infer that this is the correct tool only when LUCA-specific pricing is wanted.

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