Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SN28

Paid. gm (SN28) 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/SN28.

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

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 at all, the description carries the full burden and does well: it discloses cost, accepted payment chains, absence of auth requirements, and an important error policy ('Failed calls not charged'). It omits response shape details like freshness/latency, which a paid-data tool would benefit from.

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-loaded with 'Paid.' and the core payload, then price, then access terms, then URL — no filler sentences. The telegraphic phrasing is dense but readable; the trailing bare URL is the only slightly awkward element.

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-param, no-output-schema purchase tool the description covers what is returned (price, 24h change, market-cap rank), what it costs, which chains to pay on, and that failures are free. Endpoint URL is included. Only the actual response format and payment mechanics per chain are left implicit.

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 schema offers nothing to clarify and the baseline of 4 applies. No parameter semantics are needed and none are misleadingly implied.

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 specific resource and its payload: 'gm (SN28) price: live USD price, 24h change and market-cap rank', which is enough to separate it from the hundreds of sibling buy_tok_* entries keyed to other tokens. It stops short of a clean verb ('returns'/'fetches'), but the intent is unambiguous.

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 buying context (paid, $0.05 USDC on Base or Solana, no account/API key) but never says when to pick this over an alternative such as buy_crypto_price or buy_coin_* for broader or spot price data. Usage is implied by the token specific to this tool rather than 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