Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SXT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 burden and does well: it discloses that the call is paid, the exact price, the payment chain/asset, that no auth is required, and that failed calls are not charged — a meaningful billing-risk disclosure an agent needs before spending money. It also names the upstream data sources (Coinbase Exchange with Kraken cross-check) and gives the raw endpoint URL, though it stops short of describing the response shape or latency.

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?

A single dense sentence plus short fragments, with no filler. The leading 'Paid.' front-loads the most decision-critical fact for an agent with a budget, followed by what data comes back, cost, access requirements, and endpoint.

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?

For a zero-parameter, no-output-schema tool, the definition covers everything an agent needs: the data returned, the cost and payment rail, auth requirements, failure billing policy, and the underlying endpoint. Nothing material is missing for correct invocation.

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 disambiguate and the baseline of 4 applies. The description usefully confirms the ticker is fixed inside the endpoint (SXT is baked into the URL), clarifying that no symbol argument exists.

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 a specific resource (SXT/USD live price) and enumerates the exact datapoints returned: last price, 24h open/high/low, % change, 24h and 30d volume. It is clearly distinguishable from the hundreds of sibling buy_coin_<TICKER> tools by ticker, though it does not mention the generic buy_crypto_price sibling that could overlap with this price-feed behavior.

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?

Cost and access conditions ($0.10 USDC on Base, no account, no API key, failed calls not charged) tell the agent what it takes to invoke, which implicitly frames when this is viable. However there is no explicit when-to-use guidance versus alternatives such as buy_crypto_price or any free price sibling, and no statement of when not to call it.

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