Skip to main content
Glama

SouthPow crypto & market data

buy_coin_PEPE

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does real work: it discloses the cost ($0.01 USDC on Base), that no account or API key is needed, that failed calls are not charged, and that data is sourced from Coinbase Exchange with a Kraken cross-check. It stops short of describing latency, data staleness/refresh cadence, or the failure/error mode, which matter for a metered endpoint.

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?

The description is two dense sentences with the billing flag front-loaded ('Paid.') followed by the payload, the cost, the auth terms, and the endpoint. Every clause carries information; nothing is filler.

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?

With no output schema and no annotations, the description compensates by enumerating the returned fields (last price, 24h OHLC, % change, 24h and 30d volume) and naming the data sources. Only the precise response shape and error behavior are left unstated, which is a minor gap for a zero-parameter read.

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 there is no parameter meaning to add; the schema itself is an empty object. Baseline for a 0-parameter tool applies, and nothing in the description confuses the calling convention.

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 concrete resource and scope: 'PEPE/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', so an agent knows exactly what data comes back. It does not explicitly contrast itself with the hundreds of sibling buy_coin_<SYMBOL> tools or with buy_crypto_price, leaving that differentiation to the symbol embedded in 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to choose this tool over buy_crypto_price or a sibling symbol endpoint, and no exclusions. The only routing-relevant signal is the price ('$0.01 USDC on Base'), which tells the agent it is a paid call but not when paying is warranted.

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