Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LUSD

Paid. Liquity USD (LUSD) 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/LUSD.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full load and does well: it discloses that calls are paid ($0.05 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. It stops short of explaining the payment handshake itself, rate limits, or failure/refund mechanics beyond the one-line promise.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Six short clauses, each earning its place: payload contents, price, payment rails, auth model, failure policy, endpoint. Payment cost is front-loaded right after 'Paid.' with no filler.

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-param, no-output-schema price lookup, the description tells the agent what data comes back, what it costs, and that no auth is required — nearly everything needed to call it correctly. The remaining gap is the mechanics of actually settling the USDC payment, which matters because the tool has no annotations to fall back on.

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?

Zero-parameter tool, so the baseline is 4; the description reinforces this by stating no account or API key is needed, which confirms the agent need not supply credentials. Nothing about parameter usage is left ambiguous.

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 concrete verb-less but specific resource: the LUSD price feed, and enumerates the payload (live USD price, 24h change, market-cap rank). The token-specific naming makes it distinguishable from the hundreds of buy_tok_* siblings, though it never explicitly contrasts itself with adjacent feeds like buy_crypto_price or buy_stable_*.

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 price-feed framing and the payment terms, so an agent can infer when the tool applies. However, there is no explicit when-to-use / when-not-to-use guidance relative to the many overlapping price siblings, and no statement of what happens if the agent needs a different asset.

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