Skip to main content
Glama

SouthPow crypto & market data

buy_coin_LMTS

Paid. LMTS/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/LMTS.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 meaningful work: it discloses cost ($0.05 USDC on Base), payment rail, that no account or API key is needed, that failed calls are not charged, and that data is sourced from Coinbase Exchange with a Kraken cross-check. What it omits is the response shape/format and any freshness or rate-limit behavior, so an agent still cannot predict what the payload looks like before paying.

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?

Extremely dense and front-loaded: cost and asset scope come first, then the returned fields, then payment/auth terms, then the URL. The telegraphic style ('Paid.', '24h open/high/low') is efficient, though a couple of fragments would read more clearly as full clauses and the raw URL adds little for an agent invoking the tool by 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 zero-parameter, no-output-schema tool, the description substitutes well by enumerating the exact returned metrics and spelling out the payment and auth model. The main residual gap is return format and latency/freshness, which matter here because the call is paid and non-refundable only on failure.

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 nothing for the description to disambiguate. The endpoint URL is included, which is slightly redundant but harmless.

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 states a specific resource and scope: live LMTS/USD price with an enumerated field list (last, 24h open/high/low, % change, 24h and 30d volume). It also implicitly resolves the mismatch between the 'buy_coin' verb and the read-only price data by leading with 'Paid.' and quoting a price. It does not explicitly say 'this is the LMTS variant of the buy_coin family, use other buy_coin_<TICKER> tools for other assets', so sibling differentiation rests on the ticker in the name.

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 rather than stated: an agent can infer it should call this when it needs LMTS/USD pricing, and the '$0.05 USDC on Base' plus 'No account, no API key' lines tell it what is required to proceed. There is no explicit when-not-to-use guidance and no named alternative (e.g. a cheaper non-LMTS price tool or buy_crypto_price) for comparison.

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