Skip to main content
Glama

SouthPow crypto & market data

buy_coin_LTC

Paid. LTC/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.05 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/LTC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 a good job: it discloses the pay-per-call price and currency, the settlement chain, that no credentials are required, that failed calls are not charged, and which exchanges the data comes from. What it does not cover is latency/freshness of the quote or whether payment is settled before or after data delivery — material for 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.

Conciseness4/5

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

Two dense sentences, no filler; pricing, entitlement, and payload are all front-loaded before the URL. The one-word 'Paid.' opener is a slightly clumsy hook, and the bare URL at the end could be labeled as an 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?

With no output schema and no annotations, the description supplies the field list, the data provenance, the cost model, and the access requirements — enough for an agent to decide and call. Gaps are the response shape (JSON keys, timestamps, units) and error behavior beyond 'failed calls not charged'.

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 the baseline is 4 and there is no parameter meaning to add. The description instead documents the returned fields, which is the useful analogue for a no-arg tool.

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 specific resource and scope: live LTC/USD last price, 24h open/high/low, % change, 24h and 30d volume, with named upstream sources (Coinbase Exchange, Kraken cross-check). It implicitly distinguishes itself from the hundreds of buy_coin_* siblings by naming the asset, though it never explicitly frames the comparison. Not quite a 5 because the leading word 'Paid.' obscures the verb rather than stating 'retrieves' or 'returns'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the commercial/auth preconditions ('$0.05 USDC on Base. No account, no API key') but gives no guidance on when to pick this over the generic sibling buy_crypto_price or over any other buy_coin_* tool. There are no exclusions, no prerequisites for payment setup, and no note about what happens if the agent lacks USDC on Base.

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