Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FLOW

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does well: it discloses the price ($0.25 USDC), the payment rail (Base), that no account or API key is required, and that failed calls are not charged. Gaps remain around rate limits, data freshness/latency, and whether the charge is per request or per successful response, 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?

Every element earns its place: cost, data contents, sources, payment rail, auth requirements, billing policy, and endpoint URL. The style is telegraphic fragments ('Paid.' as an opener) which front-loads the cost signal effectively but reads slightly clipped rather than fully structured.

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 paid quote endpoint with no output schema, the description covers what an agent needs: what data comes back, what it costs, how to pay, and that failures are free. It stops short of describing the response shape (field names, units, timestamp) which matters since 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, so the baseline is 4. The description reinforces this by stating 'No account, no API key', confirming the call needs no inputs, though it does not explicitly say the call takes no arguments at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource (FLOW/USD) and enumerates the returned fields: last price, 24h open/high/low, percent change, and 24h/30d volume. It also names the upstream sources (Coinbase Exchange with Kraken cross-check), which no sibling tool discloses, so an agent can distinguish this from the generic buy_crypto_price without opening any schema.

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 paid framing and the '$0.25 USDC on Base' line imply this is a per-call paid quote endpoint, so when to call it (need a FLOW spot quote and willing to pay) is inferable. However, the description never states when to prefer it over buy_crypto_price or any other sibling, and gives no exclusions, so guidance is only implied.

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