Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CGPT

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

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

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 provided, the description must carry the full behavioral burden, and it does much of that: it discloses the exact charge ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged. What it leaves out is whether the price is cached or how current it is, and nothing is said about the response payload shape; still, this is well above the annotation baseline.

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?

Four short telegraphic sentences, all of them informational: what you get, what it costs, what you need, and where it lives. The payment and cost details are front-loaded after the purpose, and there is no filler whatsoever.

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 tool, the description covers purpose, cost, payment method, auth requirements, failure billing, and the endpoint URL. The only meaningful omission is the freshness/latency of the quoted price, and the differentiation from the sibling coin-price tools.

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 a 4 is the baseline: there is no argument semantics for the description to explain, and every output field (price, 24h change, rank) is stated in prose. The description correctly avoids repeating anything from the empty input schema.

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-and-resource pair: it retrieves the live USD price, 24h change and market-cap rank for ChainGPT (CGPT). That is clear enough to distinguish the tool from the fetch/search siblings, but it does not differentiate itself from near-identical siblings like buy_coin_CGPT or buy_tok_CRYPGPT, which an agent must choose between using 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 Guidelines3/5

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

The word 'Paid' plus the '$0.01 USDC on Base or Solana' price does implicitly tell the agent this tool belongs to the paid tier, which gives some context about when to use it. However, it never says when to prefer this over buy_coin_CGPT, nor does it say what to avoid, such as not calling it repeatedly for the same quote; that selection still has to be inferred.

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