Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GHO

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

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

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 behavioral burden and does a solid job: it discloses the paid model, the exact cost and accepted chains (Base or Solana), that failed calls are not charged, and the endpoint URL. What is missing is data freshness/latency, whether the price is aggregated across venues, and any rate limits or retry semantics.

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?

Front-loads 'Paid' so cost is the first thing an agent sees, then payload, then price/rails, then failure policy. Five short fragments, no filler. Minor weakness: the raw endpoint URL adds little for an agent that invokes the tool rather than fetching URLs.

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, annotation-free, output-schema-free purchase tool, the description covers the three things that matter: what data comes back, what it costs and on which chains, and what happens on failure. It only lacks freshness expectations and any differentiation from the near-identical GHO/stablecoin siblings.

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 there is nothing for the description to disambiguate; the baseline applies. The description still usefully clarifies that the symbol is fixed (GHO) rather than user-supplied, which confirms no input is expected.

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?

Names a specific resource (GHO) and spells out exactly what is returned: live USD price, 24h change and market-cap rank. It is clearly a per-token price purchase, but it never distinguishes itself from the closely related siblings buy_stable_gho, buy_crypto_price or the buy_coin_* family, so an agent cannot tell from the text alone which of those to pick.

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 only implied: the description tells you it is a paid price lookup, the price ($0.05 USDC on Base or Solana) and that no account or API key is needed, which implies 'use when you need GHO spot data and can pay on-chain'. There is no explicit when-to-use versus buy_stable_gho or buy_crypto_price, and no stated exclusions or prerequisites beyond the payment requirement.

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