Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LISUSD

Paid. Lista USD (LISUSD) 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/LISUSD.

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

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 the paid model ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — all material behavior for a paid call. It omits rate limits and data freshness/latency, which would matter for a 'live' price.

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?

Six short clauses, front-loaded with the paid-flag and the data content, then cost, then endpoint. Nothing is redundant. The telegraphic style ('Paid.') is slightly clipped but functional, and the raw URL at the end is low-value for an agent that never passes it as a parameter.

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 lookup, the description covers the essentials: what data comes back, what it costs, how to pay, and that failures are free. Missing only freshness/latency and an explicit differentiation from the many sibling price tools, which keeps it short of 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 there is no parameter semantics to explain; the baseline applies. The description correctly avoids inventing parameters (the ticker is baked into the tool name) and instead spends its words on what the call returns.

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 resource precisely (Lista USD / LISUSD) and states exactly what the payload contains: live USD price, 24h change, market-cap rank. An agent knows what it gets without opening anything. It does not, however, distinguish this from siblings such as buy_crypto_price or the buy_coin_* family, which overlap in function.

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 content list (use when you need a LISUSD spot quote with 24h change) and by the payment terms, but there is no explicit 'use this instead of X' guidance against ~800 sibling price/research tools. An agent must infer the choice from the ticker in the name alone.

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