Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SBC

Paid. Stable Coin (SBC) 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/SBC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations to lean on, the description carries the full behavioral load and does well: it discloses that the call is paid ($0.05 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. What it omits is how the payment is actually transacted (e.g. whether the client handles it silently) and whether there are rate limits or data-freshness guarantees.

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?

Five short, front-loaded fragments with zero filler: payload, price, payment rails, auth requirements, failure policy, endpoint. Each sentence earns its place and nothing is repeated from structured fields.

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 lookup, the description covers the return contents, cost, payment chain, auth posture, and failure policy. The one remaining gap is the mechanics of paying the $0.05, which an agent may need to know before invoking a paid endpoint.

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?

There are zero parameters, so the schema baseline is 4. The description adds the meaningful fact that the token is fixed to SBC and embedded in the endpoint URL, confirming no symbol argument is needed or accepted.

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 (the SBC stablecoin's live USD price) and enumerates the returned fields (price, 24h change, market-cap rank), so an agent knows exactly what it gets. It does not, however, differentiate itself from adjacent siblings such as buy_stable_* entries or buy_crypto_price, leaving the symbol-to-tool selection to the tool name 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?

Usage is only implied: an agent can infer this is the SBC-specific price call because the symbol is baked into the name and the URL. There is no explicit statement of when to prefer this over buy_stable_SBC-style siblings, buy_coin_*, or buy_crypto_price, and no prerequisites or exclusions are given.

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