Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BASED1

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

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

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 behavioral burden and does noticeably well: it discloses the price ($0.25 USDC on Base), that failed calls are not charged, the absence of auth, the upstream sources (Coinbase Exchange with Kraken cross-check), and the endpoint. Not covered: how payment is actually settled (signature? pre-funded balance?), latency, or rate limits.

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?

Extremely dense and front-loaded: cost and data scope lead, then payment, auth, failure policy, and endpoint. Every clause carries information an agent would otherwise have to guess, and there is no 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?

No output schema exists, and the description compensates by enumerating the returned fields and their upstream sources, so an agent knows what it buys. Payment and failure semantics are present. The remaining gap is the mechanics of how the USDC charge is executed, which matters for a paid call.

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 and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies.

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 exact asset pair (BASED1/USD) and enumerates the payload: last price, 24h open/high/low, % change, 24h and 30d volume. Against hundreds of near-identical buy_coin_* siblings, the explicit ticker and data list are what an agent needs to select correctly. It stops short of a clean verb phrase ("Paid. BASED1/USD live:" relies on the name to supply the action), which keeps it out of the top band.

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 by the data described — call this to get a BASED1 spot snapshot. The description also says no account or API key is needed, which removes a common blocker. But it never contrasts with alternatives such as buy_crypto_price or a free source, and gives no guidance on when a paid call is warranted versus a cheaper sibling.

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