Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SNT

Paid. Status (SNT) 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/SNT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden, and it does substantial work: it discloses pay-per-call billing ($0.05 USDC on Base or Solana), that no credentials are required, and the important billing trait that failed calls are not charged. It stops short of describing data freshness, rate limits, or failure modes, which are relevant for a live-price endpoint.

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?

Six short fragments, front-loaded with the paid flag, then the payload, then price and access terms. Each element (cost, chains, no key, no charge on failure) is decision-relevant, and nothing is padded.

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 tool, the description covers payload contents, cost, payment chains, auth requirements, and billing on failure — enough to invoke it confidently. The only gap is freshness/refresh cadence for a 'live' price, which an agent would want before trusting the number.

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 baseline is 4 and there is no parameter meaning to add or omit. The description instead pins down what the fixed call returns, which is the only semantic surface available.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and verb-equivalent: Status (SNT) price, with the exact fields returned (live USD price, 24h change, market-cap rank). Against a sibling list of hundreds of buy_tok_* and buy_coin_* entries, naming the token and payload explicitly lets an agent pick this one without opening anything else.

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 'Paid' prefix plus the $0.05 USDC cost and 'no account, no API key' context imply this is a pay-per-call endpoint to use when SNT pricing is needed. However, it never states when to prefer this over a general sibling such as buy_crypto_price, nor any exclusions, so usage selection is left to inference.

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