Skip to main content
Glama

SouthPow crypto & market data

buy_coin_LIGHTER

Paid. LIGHTER/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.25 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/LIGHTER.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 the cost, the payment asset and chain, that no credentials are required, that failed calls are free, and the upstream sources (Coinbase Exchange with Kraken cross-check). Missing only operational details like rate limits, freshness/caching, or error/response format.

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 'Paid.' lead is front-loaded and the sentence that follows packs the data fields, pricing, auth model, and failure policy without filler. The raw URL at the end is slightly abrupt but is genuinely actionable information for an agent.

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 priced data endpoint with no output schema, the description covers cost, access, sources, and returned fields, which is nearly everything needed to call it. It stops short of stating the response format and what a non-200 or paid-but-empty result looks like.

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 schema baseline of 4 applies; the symbol is baked into the endpoint rather than being an argument. The description correctly adds no parameter prose and instead documents the return fields and endpoint URL.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the concrete resource (LIGHTER/USD live price) and enumerates exactly which fields come back: last price, 24h open/high/low, % change, 24h and 30d volume. That distinguishes it from the hundreds of sibling buy_coin_<SYMBOL> tools, which otherwise carry no descriptive text at all.

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?

Commercial and access preconditions are spelled out ('$0.25 USDC on Base', 'No account, no API key', 'Failed calls not charged'), which is real usage guidance for deciding whether to call it. However, there is no statement of when to prefer this over related siblings such as buy_crypto_price or a different symbol variant, and no exclusions.

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