Skip to main content
Glama

SouthPow crypto & market data

buy_coin_YFI

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 does reasonably well: it discloses cost, payment rail, credential-free access, no-charge-on-failure, and the underlying data sources (Coinbase Exchange with Kraken cross-check). It stops short of stating the response format or latency/rate limits, which would matter for an agent deciding whether to pay.

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 the paid flag, then the data payload, then cost/access, then the URL — an efficient ordering with essentially no filler. The telegraphic phrasing ('Paid.', '% change') is dense but unambiguous.

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 must convey both behavior and returns, and it enumerates the metrics plus sources and payment terms. The main residual gap is response format and whether the quoted price is a snapshot or a range, but for a simple single-value price feed this is close to sufficient.

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?

Zero input parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. The description correctly implies the ticker is baked into the endpoint rather than supplied as an argument.

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 the exact resource (YFI/USD) and enumerates the returned fields (last price, 24h open/high/low, % change, 24h and 30d volume), which lets an agent know precisely what this returns. Sibling differentiation is carried only by the ticker in the name and the URL; the description never contrasts itself with buy_crypto_price or other buy_coin_* tools.

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?

The payment mechanics (paid, $0.05 USDC on Base, no account/API key, failed calls not charged) tell the agent how to use it, which is useful. But there is no explicit when-to-use/when-not guidance versus the generic buy_crypto_price or the hundreds of other ticker tools, so selection is implied by the ticker alone.

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