Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GNO

Paid. GNO/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.10 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/GNO.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description supplies important behavioral details itself: a $0.10 USDC charge on Base, no account or API key requirement, no charge for failed calls, and Coinbase Exchange data with a Kraken cross-check. It does not explain how payment is authorized or executed, so the disclosure is strong but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The compact fragments each contribute distinct information: data scope and fields, sources, fee and network, authentication requirements, failure charging, and endpoint. There is no filler or substantive repetition.

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 simple zero-input quote tool, it covers the expected metrics despite the absence of an output schema and also documents provenance and commercial behavior. The main remaining gaps are payment-flow details and explicit routing guidance versus the more general buy_crypto_price sibling.

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?

There are no parameters to document, so the zero-parameter baseline applies. The fixed GNO/USD pair and asset-specific URL reinforce that the tool is preconfigured rather than requiring a symbol or currency argument.

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 identifies a live GNO/USD market-data lookup and enumerates its price, open/high/low, percentage-change, and volume metrics, with named sources. This clarifies that the potentially misleadingly named tool provides paid price data rather than purchasing GNO, though it does not explicitly differentiate it from buy_crypto_price.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The fixed asset, USD pair, and 'live' scope make it clear to select this tool for current GNO quote and volume information, while 'Paid' establishes the commercial context. It provides no explicit when-not guidance or alternative tool for other assets or workflows.

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