Skip to main content
Glama

SouthPow crypto & market data

buy_tok_0G

Paid. 0G (0G) 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/0G.

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

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 supplied, the description carries the full behavioral burden and does fairly well: it discloses the price ($0.01 USDC), the accepted chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — the last point being materially useful before invoking a paid endpoint. It does not say how payment is settled automatically, whether a 402 challenge is returned, or what a failure response looks like.

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?

Compact and front-loaded: asset and payload first, then pricing, then trust/access conditions. The '0G (0G)' duplication and the trailing bare URL are the only slight waste; everything else earns its space.

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-argument paid lookup with no output schema, the description covers the essentials: what fields come back, what it costs, on which chains, and that failures are free. The remaining gap is operational — how the paid call is actually completed and how fresh the quote is — which matters for an agent deciding to spend money.

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 no parameters, so there is nothing for the description to explain beyond what the empty schema already conveys; baseline credit applies. The description does correctly avoid implying any hidden inputs.

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 asset (0G), the exact data returned (live USD price, 24h change, market-cap rank), and the endpoint, so the purpose is unambiguous. It stops short of differentiating itself from the many sibling buy_tok_* and buy_coin_* price tools, notably buy_tok_OG which appears to target the same asset, so the agent cannot rule out a duplicate from the description 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?

Usage is implied by the data listed — call this when you need 0G's spot price, 24h move, or rank — and the payment terms clarify the cost of doing so. There is no explicit when-to-use vs. buy_crypto_price or vs. buy_tok_OG, and no stated freshness or rate limit that would tell an agent when this is the better source.

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