Skip to main content
Glama

SouthPow crypto & market data

buy_coin_STG

Paid. STG/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/STG.

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

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 at all, the description carries the full burden and does real work: it discloses that the call is paid, the exact cost and payment currency/chain, that no authentication is needed, and that failed calls are not billed. It still omits the mechanics of payment (how USDC is charged), latency, and any rate limits, which for a monetized endpoint would be valuable.

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?

Front-loaded with 'Paid.' so cost is the first thing an agent sees, then payload fields, then price/terms, then the endpoint. Every clause is a distinct fact with no repetition; the telegraphic style suits a high-volume sibling family where descriptions are scanned quickly.

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?

Because there is no output schema, the description must enumerate return values, and it does so (last price, 24h OHLC, % change, 24h/30d volume). Cost, auth, and failure billing are all covered for a monetized tool. It would be stronger with a note on response shape or error behavior, but nothing essential for calling it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no input semantics for the description to clarify; the baseline for a 0-param tool applies. The endpoint URL is embedded in the text as informational rather than as an argument, so it adds no schema-level meaning.

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?

States a concrete deliverable: live STG/USD price plus 24h open/high/low, % change, and 24h/30d volume, with named sources (Coinbase Exchange, Kraken cross-check). This also implicitly disambiguates the misleading 'buy_coin_' prefix by making clear the payload is price data, not a token purchase. It does not distinguish itself from the generic sibling buy_crypto_price, which is the one overlap an agent could stumble on.

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?

The price ($0.10 USDC on Base), the lack of account/API-key requirements, and the no-charge-on-failure policy give practical invocation context. However, it never says when to prefer this over buy_crypto_price for STG quotes, nor any conditions where the call should be avoided. Usage is inferable from the ticker but not explicitly routed.

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