Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SOL

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

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

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 does well: it discloses paid pricing ($0.01 USDC on Base), payment rail, no account or API key required, that failed calls are not charged, the exact endpoint URL, and upstream data sources. It omits freshness/latency and rate limits, which keeps it below a 5.

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?

It is front-loaded and dense: payment, payload, sources, price, auth, failure policy, URL. The telegraphic fragments ('Paid.', '$0.01 USDC on Base.') read as terse but each carries information; nothing is filler.

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 read tool with no output schema, the description covers what the returned fields are, where the data comes from, what it costs, and what happens on failure. Missing call cadence/price freshness and the response envelope are the only notable gaps.

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 nothing to disambiguate; baseline 4 applies. The description correctly implies no arguments are needed by giving a fixed per-coin endpoint.

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 and payload: SOL/USD live price with 24h open/high/low, percent change, and 24h/30d volume, plus named sources (Coinbase Exchange, Kraken cross-check). That is enough to tell it apart from the hundreds of buy_coin_<TICKER> siblings, but the name 'buy_coin_SOL' implies purchasing a coin while the description describes a data fetch, and no verb is stated outright.

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: call this when you need live SOL/USD spot data. There is no explicit when-to-use or when-not-to-use guidance and no reference to the generic sibling buy_crypto_price, which an agent could reasonably confuse with this one.

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