Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SB

Paid. Snowbank (SB) 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/SB.

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

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 no annotations, the description must carry the behavioral load, and it does a solid job by disclosing the paid pricing model, accepted payment chains, the absence of auth requirements, and the no-charge-on-failure policy. It stops short of describing response latency, rate limits, or freshness guarantees, which matters for a live price feed.

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 telegraphic but front-loaded: the payload comes first, then payment terms, then the endpoint. Every clause carries information, though the fragmented style takes a second pass to parse and could flow more naturally.

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, paid, read-only price lookup with no output schema, the description covers everything needed to call it correctly: what it returns, what it costs, how to pay, that no auth is required, and the endpoint URL. There is no meaningful gap left for an agent to guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 applies. The description correctly implies the symbol is fixed rather than caller-supplied, which prevents an agent from trying to pass a ticker argument.

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 (Snowbank/SB) and enumerates the actual payload: live USD price, 24h change, and market-cap rank. That is enough to distinguish it from unrelated siblings, but it never contrasts itself with the very similar buy_coin_* and buy_crypto_price tools, so an agent must infer the difference from the token symbol alone.

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?

It gives the practical call context clearly: $0.05 USDC on Base or Solana, no account or API key required, failed calls not charged, plus an explicit URL. What is missing is routing guidance — nothing says when to pick this over buy_crypto_price or the buy_coin_* family for the same underlying asset.

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