Skip to main content
Glama

SouthPow crypto & market data

buy_coin_LINK

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

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

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 usefully discloses the $0.01 USDC charge on Base, the absence of account and API-key requirements, no charge for failed calls, and exchange sourcing with a Kraken cross-check. It does not explicitly establish that the operation is read-only market-data retrieval rather than a trade, nor explain payment handling or response behavior.

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?

Compact, front-loaded fragments convey scope, fields, sources, price, authentication, failure billing, and endpoint with almost no filler. The wording is telegraphic but easy to scan and appropriately sized.

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-input price lookup, the definition covers the returned metrics, provenance, cost, and basic invocation prerequisites, partly compensating for the missing output schema. Remaining gaps include response format and payment flow, plus an explicit statement that the tool does not buy or sell LINK.

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 has zero parameters, so there are no undocumented inputs requiring explanation. The fixed pair and URL confirm that invocation is hard-coded to LINK/USD, providing useful context beyond the empty schema.

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 identifies a paid live LINK/USD market-data lookup and enumerates its metrics and sources, distinguishing it from other asset-specific siblings. However, it lacks an explicit retrieval verb and does not clarify that no LINK purchase occurs, which would be helpful given the tool 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?

"LINK/USD live" implies use when current LINK pricing and volume data are needed, while the fee disclosure helps assess whether a paid call is acceptable. There is no explicit when-not guidance or comparison with buy_crypto_price or other price-data alternatives.

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