Skip to main content
Glama

SouthPow crypto & market data

buy_coin_LDO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose genuinely useful facts beyond structure: the price ($0.10 USDC on Base), that failures are not charged, that no account or API key is required, and the upstream sources (Coinbase Exchange with Kraken cross-check). It stops short of stating latency, rate limits, response format, or what a failure actually looks like, so the disclosure is solid but not complete.

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?

Front-loads 'Paid.' so the cost consideration is impossible to miss, then packs data contents, source, price, and no-key terms into a single dense sentence with zero filler. Every clause carries information an agent would otherwise have to discover by calling the 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?

No output schema exists, so the description must describe the return payload, and it enumerates the fields returned (last price, 24h OHLC, % change, 24h/30d volume). It is complete enough to call correctly and interpret the result; only the failure response shape and rate/latency behavior remain unspecified.

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 no parameter meaning for the description to add; the baseline for a parameterless tool is 4. The description does not need to compensate for any schema gap here.

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: 'LDO/USD live: last price, 24h open/high/low, % change, 24h and 30d volume'. The ticker makes the sibling identity clear, but the description never explicitly contrasts itself with buy_crypto_price or the other buy_coin_* variants, leaving the agent to infer the differentiation from the name alone.

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 context is implied rather than stated - it is evidently a paid per-ticker price lookup, and the 'No account, no API key' note hints at zero-setup invocation. However, there is no explicit when-to-use versus buy_crypto_price, no guidance on caching or how often to call a paid endpoint, and no exclusion conditions.

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