Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LITY

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

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

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 real work here: it declares the tool is paid, states the exact cost ($0.01 USDC) and accepted chains (Base or Solana), confirms no account or API key is needed, and specifies that failed calls are not charged — a genuinely useful billing guarantee. It omits response freshness, rate limits, and the payment protocol, which keeps it below 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?

The critical constraint 'Paid.' is front-loaded, followed by payload, cost, auth posture, failure policy, and endpoint — a sensible order with almost no waste. Minor nits: the 'LITY (LITY)' duplication and the raw URL are slightly noisy, though the URL is arguably actionable 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, no-output-schema, no-annotation tool, the description covers what an agent must know: what comes back, what it costs, where to pay, and that failures are free. What is missing is how 'market-cap rank' is scoped (global vs. some universe) and how fresh the quote is.

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 for the description to disambiguate and the baseline of 4 applies. The description correctly spends no words on input semantics and instead documents the output fields.

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 (LITY live USD price) and enumerates the payload fields it returns: 24h change and market-cap rank. That payload detail distinguishes it from the many sibling buy_tok_* endpoints. It lacks an explicit verb and never contrasts itself with the generic buy_crypto_price sibling, which leaves a small routing gap.

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 by the token symbol — an agent infers 'call this when you want LITY price data.' There is no statement of when to prefer it over buy_crypto_price or the buy_coin_LTC-family tools, and no note on whether it accepts only single-token lookups. The purchase mechanics are described, but the selection logic is not.

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