Skip to main content
Glama

SouthPow crypto & market data

buy_coin_LPT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does meaningful work: it discloses that the call is paid ($0.10 USDC on Base), requires no account or API key, and that failed calls are not charged — all behavior an agent could not infer from an empty schema. It omits latency, rate limits, and caching/refresh cadence of the 'live' data.

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-loaded with cost ('Paid.') and then the payload, with no filler sentences. The telegraphic, fragment-heavy style is efficient but slightly clipped, and the trailing raw URL is more useful to an integrator than to a model choosing a tool.

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 data-fetch tool with no output schema, the description covers what is returned, what it costs, how billing failure works, and the source venues — enough to call it correctly. The main omission is any indication of response shape or freshness guarantees, which matters because no output schema exists.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The ticker is baked into the tool identity, so no argument-level semantics are needed.

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 names the specific resource (LPT/USD) and enumerates exactly what comes back: last price, 24h open/high/low, % change, 24h and 30d volume, plus the source venues. That is far more than a restatement of the name. It does not explicitly say how it relates to the hundreds of sibling buy_coin_* tools or to buy_crypto_price, so it stops short of a 5.

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 content ('live LPT/USD price data'), and the payment terms imply a pay-per-call context. However, there is no explicit when-to-use, no statement of when NOT to use it, and no pointer to buy_crypto_price or other alternatives for price data, which is a real gap given the sibling set.

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