Skip to main content
Glama

SouthPow crypto & market data

buy_tok_STON

Paid. STON (STON) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/STON.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses that the call is paid, the exact cost ($0.01 USDC), accepted payment chains (Base or Solana), that no authentication is needed, that failed calls are not charged, and the underlying endpoint URL. Missing details are rate limits, latency, and how non-failure errors such as partial responses are billed.

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?

The description is compact and front-loaded: payment status first, then the payload, then cost, then auth and billing terms, then the URL. Every clause carries information. The redundant 'STON (STON)' and the raw URL are slightly wasteful but not harmful.

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 paid endpoint with no output schema, the description covers everything an agent needs before calling: price, payment method, auth requirements, failure billing, and returned fields. Only secondary operational details, such as rate limits or response format, are absent, which is a minor gap at this complexity level.

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; the baseline of 4 applies. The description correctly implies a fixed, single-token query with no filtering options.

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 exact resource and its payload: 'STON (STON) price: live USD price, 24h change and market-cap rank.' That lets an agent distinguish this from the hundreds of buy_tok_* siblings by ticker. It does not, however, differentiate itself from the generic buy_crypto_price sibling, which likely covers the same data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states prerequisites (paid, no account, no API key) but gives no when-to-use or when-not guidance. An agent is left to infer whether this is preferable to buy_crypto_price or the buy_coin_STON variant. No alternative is named, and no exclusion is stated.

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