Skip to main content
Glama

SouthPow crypto & market data

buy_coin_PUMP

Paid. PUMP/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.002 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/PUMP.

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

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 supplied, the description carries the full burden and does so well: it discloses the payment model and price, the chain and currency, that no account or API key is required, that failed calls are free, and the upstream data sources (Coinbase Exchange with Kraken cross-check). Gaps remain on rate limits, response encoding, and price precision, which keeps it short of a 5.

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?

Two dense sentences/fragments, front-loaded with the most decision-critical fact ('Paid'), followed by data content, cost, auth requirements, and the endpoint URL. No filler and no repetition of the tool name.

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?

No output schema exists, so the description must convey return values, and it does by listing every field returned and the two exchanges used. For a zero-parameter, read-only price lookup this is nearly complete; only the wire format (JSON shape, timestamp field, unit conventions) is left unstated.

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 baseline is 4 and there is no parameter meaning for the description to add. The description correctly spends its words on cost and data content instead of inventing parameter guidance.

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 (PUMP/USD) and enumerates the returned data points: last price, 24h open/high/low, % change, 24h and 30d volume. It is unambiguous about what the tool yields. It doesn't explicitly contrast with sibling tools, but the ticker in the tool name plus the explicit 'PUMP/USD' in the description makes the per-coin specialization obvious.

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?

There is no explicit when-to-use or when-not statement, and no named alternative such as buy_crypto_price is mentioned. However, the upfront 'Paid' marker plus the exact price ($0.002 USDC on Base) and 'Failed calls not charged' give the agent what it needs to make a cost-based decision before calling.

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