Skip to main content
Glama

SouthPow crypto & market data

buy_cp_privacy

Paid. Live crypto prices, privacy basket (XMR, ZEC, DASH, ROSE): USD median of Coinbase and Kraken, each source shown. $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/crypto-prices/privacy.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 burden and does substantial work: it discloses the paid model, the exact cost ($0.002 USDC), the accepted payment chains (Base or Solana), the absence of accounts or API keys, a failure policy (failed calls not charged), and data provenance including how the value is aggregated. It falls short only on return shape details beyond 'each source shown' and on any rate-limit or latency information.

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 text is dense and front-loaded, leading with the billing fact and then the payload, with the endpoint URL last where it belongs. The telegraphic fragment style ('Paid.', '$0.002 USDC on Base or Solana.') costs a little readability but wastes no words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-annotation tool with no output schema, the description covers cost, payment mechanics, provenance and covered assets well. What it does not cover is what the response actually looks like (field names, per-source breakdown structure) or whether the price is a spot snapshot, which matters for an agent deciding whether to cite the result.

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 for the description to disambiguate and the baseline of 4 applies. The prose correctly implies that no arguments need to be assembled, since the basket and quote currency are fixed by the 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 concrete resource and its exact contents: a privacy-coin basket covering XMR, ZEC, DASH and ROSE, with a stated aggregation method (USD median of Coinbase and Kraken). That is enough to separate it from generic siblings such as buy_cp_majors or buy_cp_defi, though the differentiation is implicit rather than 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 inferable from the coin list and the price point, but there is no explicit when-to-use or when-not guidance. It never says whether to prefer this basket over the per-coin siblings (buy_coin_ZEC, buy_coin_DASH, buy_coin_ROSE) that appear alongside it, leaving the routing decision to the agent.

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