Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LRC

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

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

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 at all, the description carries the full burden and does well: it discloses the cost, the accepted payment chains, that no authentication or account is required, and the important risk mitigation that failed calls are not charged. Missing are details like rate limits or data freshness/refresh cadence, which matter for a live price feed.

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-loads the critical 'Paid' flag, then states the resource and returned fields, then commercial terms. Every clause carries information an agent needs before calling. The trailing raw URL is slightly clunky but is the only minor redundancy given the description already names the endpoint.

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 no-parameter, no-output-schema tool, the description must describe both the result payload and the transaction model, and it does: price, 24h change, market-cap rank, cost, chains, and charge-on-success semantics. It stops short of describing response shape or data latency, and does not address overlap with the sibling buy_coin_LRC.

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; the baseline of 4 applies. The description correctly makes clear that no arguments are needed by specifying the ticker and payment details up front.

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?

States exactly what the tool retrieves: Loopring (LRC) live USD price, 24h change and market-cap rank. The ticker is named explicitly, so an agent can distinguish it from the hundreds of other buy_tok_* and buy_coin_* siblings without inspecting any schema.

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?

Gives commercial context ('Paid', '$0.05 USDC on Base or Solana') and prerequisites ('No account, no API key'), which implies a paid alternative to free pricing tools. However, it never states when to choose this over the clearly related free-looking sibling buy_coin_LRC or buy_crypto_price, leaving the routing decision to inference.

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