Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PINKSALE

Paid. PinkSale (PINKSALE) 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/PINKSALE.

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

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 supplied, the description carries the full behavioral burden and does a decent job: it declares the tool is paid at $0.01 USDC on Base or Solana, that no account or API key is needed, that failed calls are not charged, and it exposes the backing endpoint URL. The remaining gap is billing mechanics beyond the headline price, such as whether repeated calls are metered or rate-limited.

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?

Five short, front-loaded fragments: paid flag, what you get, what it costs, auth posture, failure billing, then the URL. Telegraphic style ('Paid.') is slightly clipped but every clause carries information 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 price tool with no output schema, the description covers the essential decision inputs: what is returned (price, 24h change, market-cap rank), what it costs, how payment works, and how failures are billed. A slightly richer statement of the response shape or freshness would close the remaining gap.

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 imposes nothing to explain and the baseline is 4. The description correctly spends no words on inputs and instead characterizes what the single call returns.

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?

States a specific verb and resource: fetch the PinkSale (PINKSALE) live USD price, plus 24h change and market-cap rank. That is materially more precise than the majority of the buy_tok_* siblings, which carry no description at all. It does not explicitly frame itself as one member of a per-ticker family, so differentiation from buy_crypto_price or buy_coin_* is left to the name.

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 implied rather than stated: it is a paid, single-token price lookup. There is no explicit when-to-use or when-not guidance, and no pointer to sibling tools such as buy_crypto_price or buy_tok_<other ticker> for different assets. The practical prerequisites (no account, no API key) are stated, which partially compensates.

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