Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SFP

Paid. SafePal (SFP) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/SFP.

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

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 disclosure burden and does well: it marks the tool as paid, states the exact price ($0.01 USDC on Base or Solana), confirms no account or API key is required, guarantees failed calls are not charged, and exposes the endpoint URL. It omits latency/freshness of the quote and rate-limit behavior, which are the remaining gaps for a paid data call.

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?

Six short clauses, front-loaded with the 'Paid' flag and then the payload, cost, access conditions, billing guarantee, and URL. Every sentence carries information an agent needs before spending money, with 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?

For a no-parameter, no-output-schema tool it covers the essentials: what data returns, what it costs, which chains settle payment, and that failures are free. Remaining omissions are the freshness/latency of the quote and the response shape beyond the three named fields.

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?

There are zero parameters, so the baseline is 4 and there is no parameter meaning to add. The description correctly avoids inventing input options and instead fixes the token and quote currency in prose, which is the right approach for a parameterless 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 resource and the exact payload: SafePal (SFP) live USD price, 24h change, and market-cap rank. Unlike the bare tool name, it tells an agent what fields come back. It stops short of distinguishing this from the near-identical siblings buy_crypto_price or the buy_coin_* family, so an agent gets no help choosing between overlapping price tools.

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 only implied by scope: you call this when you need the SFP price snapshot. The description supplies practical context (payment amount, chains, no account, no charge on failure) but never says when to prefer this over buy_crypto_price or a buy_coin_* tool, nor any exclusion or prerequisite.

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