Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CETUS

Paid. Cetus Protocol (CETUS) 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/CETUS.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the important commercial behavior: $0.05 USDC, payable on Base or Solana, no account or API key, and 'Failed calls not charged' — a genuinely useful failure-billing guarantee for an agent. It omits any hint of response shape, latency, rate limits, or what happens on partial/unpaid requests, so the mutation-of-wallet aspect (spending USDC per call) is only partially covered.

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?

Five short clauses, front-loaded with payment status and the resource, then price, then payment mechanics, then the endpoint. Every sentence carries information an agent needs; nothing is padding.

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, output-schema-less paid endpoint, the description names the returned fields and the payment terms, which is close to everything needed to call it. Only the raw endpoint URL is given without saying whether the agent should ever call it directly versus through this tool.

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 input schema is an empty object with zero properties, so there is nothing for the description to clarify; baseline applies. The description correctly emphasizes that no credentials or arguments are needed, which reinforces the zero-parameter contract.

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?

States a specific resource and payload: 'Cetus Protocol (CETUS) price: live USD price, 24h change and market-cap rank,' which tells an agent exactly what comes back. The 'Paid.' opener disambiguates the misleading buy_ prefix. It does not distinguish itself from the large buy_coin_* / buy_crypto_price families, so an agent cannot tell from the text alone why to pick this wrapper over those.

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 implied rather than stated: it is clearly the CETUS spot-price call, and 'No account, no API key' plus the price and rails give the purchasing preconditions. There is no explicit when-to-use / when-not-to-use guidance and no routing to the obvious alternatives (buy_crypto_price, the buy_coin_* token family) that presumably cover the same underlying data.

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