Skip to main content
Glama

SouthPow crypto & market data

buy_tok_RYFT

Paid. RYFT (RYFT) 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/RYFT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 well: it discloses that the call is paid, the exact price and accepted chains, that no credentials are needed, and that failed calls are not charged. The endpoint URL is included, but rate limits and payment-flow mechanics (how the USDC transfer is completed) are left unspecified.

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 cost signal "Paid." is front-loaded and each fragment (subject, cost, chain, auth, failure policy, URL) carries distinct information. The telegraphic fragment style is dense but readable; a slightly more prose-like framing of the failure policy would read better without adding length.

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 tool, the description covers what is returned, what it costs, which chains settle payment, auth requirements, and failure billing — essentially everything needed to decide and pay. Only the mechanics of executing the payment and any rate/throttle limits are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain; the description correctly spends no words on inputs and instead documents output fields and cost, which is the right allocation for a no-arg tool.

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?

"RYFT (RYFT) price: live USD price, 24h change and market-cap rank" names the exact asset and the three fields returned, so an agent knows precisely what this fetches. Among hundreds of buy_tok_* siblings the ticker is the distinguishing token, though the description never contrasts itself with buy_crypto_price or buy_coin_* variants for the same asset.

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 and access conditions ("$0.01 USDC on Base or Solana", "No account, no API key") tell an agent whether it can call this at all, which implicitly guides usage. However, there is no explicit statement of when to prefer this over buy_crypto_price or any exclusion/alternative routing.

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