Skip to main content
Glama

SouthPow crypto & market data

buy_tok_REAL

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full burden. It does valuable work by disclosing the payment model, both supported chains, the absence of accounts/keys, and the no-charge-on-failure policy. It stops short of explaining how payment is actually authorized (no wallet or payment parameter exists), whether there are rate limits, or what a successful versus failed response looks like.

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?

A single dense sentence-block with the token identity up front, then what you get, then cost and mechanics. Every clause carries information; the raw endpoint URL is the only element of marginal value for an agent that already has the tool available, but it is short enough not to hurt.

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 price lookup, the description covers identity, returned fields, cost, payment chains and failure policy — enough to decide whether to call it. The only gap is operational detail about how the micropayment is settled, which the empty input schema leaves entirely implicit.

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; the baseline of 4 applies. Nothing in the description misleads about inputs, and the fixed URL further confirms the request shape is entirely predetermined.

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 a specific resource (RealLink / REAL) and states exactly what is returned: live USD price, 24h change and market-cap rank. That is far clearer than a bare name restatement, though it never explicitly distinguishes itself from the many sibling price tools (buy_crypto_price, buy_coin_*, buy_tok_*), so differentiation is left to the token symbol embedded in the name.

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?

It gives the commercial context for invoking it ($0.01 USDC on Base or Solana, no account or API key, failures not charged), which implies 'use this when you want REAL price data and can pay'. However, there is no explicit when-to-use versus when-not, and no pointer to a cheaper/free alternative such as buy_crypto_price among the siblings.

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