Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GPT

Paid. Gold Park (GPT) 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/GPT.

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

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 at all, the description carries the full burden and does well: it discloses that the call is paid, the exact price and payment chains, that no auth is needed, and that failures are not billed. It omits response shape details such as freshness/caching of the quote or latency, but the commercial and auth semantics are unusually explicit.

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?

The paid gate is front-loaded in a single word, followed by what the tool returns, then cost/access terms, then the URL. It is telegraphic rather than ungrammatical, and every clause conveys something actionable; only the trailing bare URL is arguably filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description lists the three fields returned and the payment/auth/failure model, so an agent knows both what it gets and what it costs before calling. For a zero-parameter, single-value paid lookup, nothing essential is missing.

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 the baseline is 4; there is nothing for the description to disambiguate. The endpoint URL is included, which is more than a no-argument schema requires.

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 resource precisely (Gold Park / GPT) and enumerates the returned data points: live USD price, 24h change and market-cap rank. It does not, however, distinguish this from the hundreds of sibling buy_tok_* endpoints or explain the buy_tok_ vs buy_coin_ naming split, so an agent must infer that GPT is simply the token-specific variant.

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 cost and access conditions ($0.01 USDC on Base or Solana, no account, no API key, failed calls not charged), which tells the agent how to call it. What it never states is when to prefer this over a sibling like buy_coin_* price feeds or buy_crypto_price, so selection among ~600 near-identical tools is left to inference from the name.

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