Skip to main content
Glama

SouthPow crypto & market data

buy_tok_LCS

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

With zero annotations, the description carries the full burden and does so well. It discloses cost ($0.01 USDC), accepted payment rails (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. That covers auth requirements, billing behavior, and failure handling — exactly the traits an agent needs before invoking a paid call.

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?

Roughly forty words with the price descriptor front-loaded and the commercial terms following. Every clause earns its place: fields returned, cost, payment chain, auth requirement, failure policy, endpoint. No filler or restatement of the name.

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 price lookup, the description supplies the returned fields, cost, payment method, and failure policy, which is nearly everything needed to call it correctly. The only gap is routing guidance among the massive buy_tok_* sibling set and the generic buy_crypto_price alternative.

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 no parameters, so there is no parameter meaning to add beyond baseline. The description correctly does not invent or imply any inputs, which is consistent with the empty schema.

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?

Names the resource precisely: 'LocalCoinSwap (LCS) price: live USD price, 24h change and market-cap rank', which tells an agent exactly which data points come back. The symbol is encoded in both name and description, so an agent can distinguish it from the hundreds of other buy_tok_* siblings by ticker. It stops short of explicitly stating the one-tool-per-symbol pattern or referencing a generic alternative like buy_crypto_price.

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 tool name and the enumerated fields: call this when you want LCS price data. Payment context ('$0.01 USDC on Base or Solana') helps an agent decide whether it can pay at all. However, there is no explicit when-not guidance and no mention of the sibling buy_crypto_price as an alternative for arbitrary tickers.

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