Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CTC

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 declares the tool is paid ($0.05 USDC on Base or Solana), needs no account or API key, and that failed calls are not charged. It stops short of rate limits, data freshness/latency, or what is returned when no price is available.

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?

A single dense line, front-loaded with 'Paid.' so the cost gate is the first thing seen, followed by payload, price, payment rails, auth, failure policy, and endpoint. No sentence is filler, and every clause adds information an agent would otherwise have to guess.

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 the important surface: what data returns, what it costs, on which chains, that no key is needed, and failure billing. The remaining gap is the payment mechanics (how the USDC charge is actually settled/attached) and data freshness, which the description never states.

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 schema has zero parameters, so the correct baseline is 4; there is nothing for the description to disambiguate. No parameter meaning is missing because no inputs exist.

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 verb-plus-resource: a paid lookup of the Creditcoin (CTC) live USD price with 24h change and market-cap rank. An agent knows exactly what data comes back. It does not, however, distinguish itself from the hundreds of buy_coin_*/buy_tok_* price siblings or from buy_crypto_price, so the many-to-one routing decision is left to the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement and no named alternative (e.g. buy_crypto_price or the buy_coin_ family) for the same data. The cost and 'failed calls not charged' notes help an agent weigh whether to spend, but that is pricing context, not selection guidance.

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