Skip to main content
Glama

SouthPow crypto & market data

buy_coin_STX

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 meaningful work: it discloses that the call is paid, the exact price and settlement chain/token (0.002 USDC on Base), that no account or API key is needed, and that failed calls are not charged. It stops short of describing the payment handshake (e.g. how the USDC is actually remitted), any rate limits, or the response shape.

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?

It is short and front-loaded with the single most decision-relevant fact ('Paid.'), followed by data coverage, cost, access requirements, and the endpoint URL. The telegraphic style is dense but readable; the 'URL https://...' sentence is the only element of marginal value, though it does help an agent understand the transport.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no input schema, so the description must convey both what is returned and what it costs, and it does: it lists the exact fields (last, 24h OHLC, % change, 24h/30d volume) and names the upstream venues. For a zero-parameter, single-endpoint data tool, an agent has everything it needs to decide and call.

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 schema leaves nothing to explain and the baseline is 4. The description correctly adds no parameter detail and instead spends its words on cost and data coverage, which is the right allocation for a parameterless endpoint.

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 resource precisely (STX/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, and 24h/30d volume, plus the data sources (Coinbase Exchange, Kraken cross-check). It is distinguishable from other buy_coin_* siblings only by the ticker embedded in the name, not by any explicit statement in the description, and the 'buy_coin' prefix misleadingly suggests a trade rather than a price read.

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 description gives purchase context ('Paid... $0.002 USDC on Base. No account, no API key. Failed calls not charged') which implies the usage conditions, but it never states when an agent should pick this over sibling tools such as buy_coin_BTC, buy_crypto_price, or other coin variants. Usage is implied by the ticker rather than explained.

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