Skip to main content
Glama

SouthPow crypto & market data

buy_tok_GOLD

Paid. Stairway to gold (GOLD) 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/GOLD.

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

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 well: it discloses that the call is paid, the exact cost and accepted chains, that no account or API key is needed, and that failed calls are not charged. It omits rate limits, latency, and response format, which keeps it from 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?

The text is short and front-loaded, leading with 'Paid' and following with the resource, price, and payment terms. Every sentence carries information, though the URL is redundant with the tool identity and the phrasing is slightly terse.

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, no-output-schema endpoint, the description covers what an agent needs to commit: the data returned, the cost and payment rails, and failure billing semantics. Only return-shape and rate-limit details are absent, which are minor for a single-value price lookup.

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 explain beyond confirming that no input is required. That matches the empty schema and warrants the baseline 4.

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 states a concrete resource (GOLD token price) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. A verb is only implied by the 'buy_' prefix rather than spelled out, and it never disambiguates from lookalike siblings such as buy_coin_GOLD or buy_insider_GOLD, 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 tool for GOLD price data, and the payment requirements ($0.05 USDC on Base or Solana, no account or API key) give useful preconditions. However, there is no explicit when-to-use/when-not-use guidance and no mention of which sibling to prefer for other GOLD-related data.

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