Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GCB

Paid. Global Commercial Business (GCB) 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/GCB.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 the paid nature, the exact price ($0.01 USDC), accepted chains (Base or Solana), absence of auth requirements, and the 'Failed calls not charged' billing guarantee, which is exactly the kind of trait an agent needs before spending. It does not describe the payment handshake or response envelope, keeping it just below a 5.

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?

It is front-loaded with 'Paid.' and then the payload, cost, auth, and billing terms in short declarative fragments, with no wasted sentences. The telegraphic style and trailing bare URL are slightly terse but each element earns its place.

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 paid endpoint with no output schema and no annotations, the description covers the three things an agent needs: what data is returned, what it costs, and how billing failures are handled. Missing only optional detail like response format or payment protocol specifics, which is a minor gap at this complexity.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The fixed token (GCB) is baked into the tool name and restated in the description, so no parameter meaning is lost.

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 gives a specific resource and payload: 'Global Commercial Business (GCB) price: live USD price, 24h change and market-cap rank', which tells an agent exactly what data comes back. It does not differentiate itself from likely-overlapping siblings such as buy_crypto_price or the buy_coin_* family, so it falls short of a 5.

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: an agent can infer this is the GCB-specific price endpoint, and the 'No account, no API key' note implies it can be called freely. There is no explicit guidance on when to prefer this over a generic price tool or over the paid category/aggregate endpoints in the sibling list.

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