Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SNX

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

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

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 zero annotations the description carries the full burden, and it does disclose meaningful behavior: payment of $0.002 USDC on Base, no authentication required, and that failed calls are not charged, which tells the agent retry-safe failure economics. It does not describe rate limits, latency, or response format beyond the field list.

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?

Front-loads the cost flag ('Paid.') and then packs the data fields, cost, auth, failure policy, and endpoint URL into two dense sentences with no filler. Dense but readable; the URL adds length for marginal benefit to an agent that cannot change the endpoint.

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 price feed, the description covers what is returned (enumerated fields), data sources, cost, and failure charging, which is enough to call it confidently. Only return-format details (e.g., numeric vs string, timestamp) are absent.

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 no parameters, which is the baseline-4 case; the description correctly implies no input is needed by stating no account or API key is required. Nothing is left ambiguous about inputs.

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?

A specific verb-plus-resource is implicit in the ticker-scoped name, and the description names the exact payload: last price, 24h open/high/low, % change, and 24h/30d volume for SNX/USD, with Coinbase as primary and Kraken as cross-check. It does not explicitly state how this differs from the general sibling buy_crypto_price, so it stops 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?

The description clarifies the preconditions for calling it (paid, no account, no API key) but never says when to prefer this over buy_crypto_price or other ticker siblings, nor any exclusion. Usage is only implied by the ticker in the name.

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