Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ACU

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

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

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 well: it discloses cost and accepted payment chains, that no authentication is required, and the important billing nuance that failed calls are not charged. It omits rate limits, latency/freshness guarantees, and response shape, which keeps it from a 5 for a paid endpoint.

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 fragments, front-loaded with the single most decision-relevant fact ('Paid.'), followed by what is returned, the price and payment rails, and the failure policy. Nothing is padded and the endpoint URL is placed last where it does not obstruct scanning.

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 lookup this covers nearly everything an agent needs: what data comes back, what it costs, how to pay, and that failures are free. The only gap is freshness/latency expectations and any usage caps, which matter somewhat for a 'live' price feed.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing parameter discussion and instead spends its words on cost and scope.

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 specific resource (Acurast / ACU) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. That is concrete enough for an agent to know what it buys, but it never distinguishes itself from close siblings such as buy_crypto_price or the buy_coin_* family, so an agent cannot route between them from this text alone.

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 context is implied by the payment details ($0.05 USDC on Base or Solana, no account, no API key, failures not charged), which tells the agent this is a per-call paid lookup. However, there is no explicit when-to-use statement and no reference to alternatives like buy_crypto_price or buy_coin_ACU, leaving the routing decision to inference.

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