Skip to main content
Glama

SouthPow crypto & market data

buy_stable_gho

Paid. GHO (GHO) stablecoin live: price vs peg, supply, 1d/7d/30d supply change, supply per chain (DefiLlama data). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/stablecoins/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_stable_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 supplied, the description carries the full burden and does well: it discloses that the call is paid, the exact price ($0.002 USDC), accepted payment chains (Base or Solana), no account or API key requirement, and that failed calls are not charged. The remaining gap is that it does not describe the response shape or freshness/latency beyond the word 'live'.

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 definition is compact and front-loads the paid nature and data scope before commercial terms. Minor waste exists in the redundant 'GHO (GHO)' and in listing the raw URL, but every other clause conveys actionable information.

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 tool with no output schema, the description covers what data comes back, what it costs, how to pay, and what happens on failure — enough for an agent to decide and invoke. Only the response format and data recency are left unspecified.

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 and there is nothing for the description to disambiguate. It correctly avoids inventing parameter guidance and instead spends its words on scope and cost.

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 exact resource (GHO stablecoin) and enumerates the payload contents: price vs peg, supply, 1d/7d/30d supply change, and per-chain supply, sourced from DefiLlama. This clearly separates it from siblings like buy_stable_dai or buy_stable_usdc. It lacks an explicit action verb (the purchase is implied by 'Paid'), which keeps it just 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 by the specificity of the coin and the data listed, but the description never states when to choose this over an alternative such as buy_cp_stablecoins-check or buy_yields_stablecoins, nor any when-not condition. The payment terms give context for whether the agent can afford the call, not for tool selection.

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