Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SAFE

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

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

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?

No annotations are supplied, so the description carries the full load, and it does disclose the non-obvious traits: it is a paid call, it costs $0.05 USDC on Base, it needs no credentials, it charges nothing on failure, and it cross-checks Coinbase Exchange against Kraken. What it omits is the payment flow itself and any latency or rate-limit expectations, so it falls short of full transparency for a metered endpoint.

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?

The description leads with the decisive word 'Paid' and then packs cost, payload, sources, and auth into a few compact clauses with no filler. The telegraphic style borders on terse, but every clause carries information an agent needs before calling.

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-argument price lookup with no output schema, the description already enumerates the returned fields and the data sources, so an agent knows what comes back. The remaining gap is the mechanics of paying the $0.05 USDC on Base, which is implied but not explained.

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, which is the baseline-4 case: there is nothing for the description to disambiguate. The description correctly reinforces this by implying the ticker and data set are fixed in the endpoint URL.

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 resource and its fields: SAFE/USD last price, 24h open/high/low, % change, 24h and 30d volume, with named sources. That is far more specific than the 300+ sibling tools, which are distinguished only by ticker suffix. It stops short of 5 because the tool is named buy_coin_SAFE while the description describes a paid price-feed endpoint, so the verb and the name do not align.

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?

Payment terms imply when this is usable: $0.05 USDC on Base, no account or API key, failed calls not charged. But the description never says when to prefer this over a sibling or over a generic price tool, and nothing frames x402 payment prerequisites. The usage context is implied by the cost disclosure rather than stated.

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