Skip to main content
Glama

SouthPow crypto & market data

buy_cp_rwa

Paid. Live crypto prices, rwa basket (ONDO, MKR, CFG, PENDLE): USD median of Coinbase and Kraken, each source shown. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/crypto-prices/rwa.

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

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 burden and does substantial work: it discloses the price ($0.01 USDC), accepted rails (Base or Solana), that no account or API key is needed, the failure-billing policy ('Failed calls not charged'), and the endpoint URL. What it omits is data freshness/latency, rate limits, and any sense of what the paid response contains beyond 'each source shown'.

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?

The critical fact ('Paid.') is front-loaded, followed by what you get, then what it costs and how payment works, then the URL. Every clause conveys a distinct operational fact with no repetition or 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 zero-parameter, no-output-schema data purchase, the definition covers basket composition, source methodology, cost, payment chain, auth requirements, billing on failure, and the URL — enough to call it correctly. The remaining gap is response shape and data freshness, which the absence of an output schema leaves entirely undocumented.

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, and the empty schema is consistent with the description's claim that no account or API key is required. No meaning is lost.

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 (live crypto prices for the RWA basket) and enumerates the four constituents (ONDO, MKR, CFG, PENDLE) plus the aggregation method, so an agent knows exactly what data it gets. It falls short of a 5 only because it never contrasts itself with the nearby siblings that also cover these tokens (buy_cp_defi, buy_coin_ONDO, buy_coin_PENDLE), leaving the basket-vs-single-coin distinction to inference.

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: an agent can infer 'call this when you want the RWA basket price' from the basket listing, and the 'each source shown' note hints at when a per-venue breakdown matters. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as buying an individual coin endpoint instead.

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