Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PEPECOIN

Paid. PepeCoin (PEPECOIN) 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/PEPECOIN.

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

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, the description carries the full burden and does well: it discloses that the call is paid, the exact price and accepted payment chains, that no account or API key is needed, and that failed calls are not charged. It stops short of stating response shape, data freshness, or latency, but the billing behavior is unusually well covered.

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?

Telegraphic and entirely front-loaded: what it returns, then cost, then payment options, then billing policy, then endpoint. No sentence is redundant and the critical 'Paid' flag leads.

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 no-parameter, no-output-schema price lookup, the description covers outputs, cost, payment rails, and failure billing. Only the actual response structure and data freshness are left unstated, which is minor given there is no output schema to fall back on.

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. The description adds nothing to explain parameters because there are none to explain, and the token is fixed by the tool name.

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 resource and outputs: 'PepeCoin (PEPECOIN) price: live USD price, 24h change and market-cap rank.' The token identity is unambiguous, but the description never distinguishes this from the near-identical siblings buy_coin_PEPE and buy_crypto_price, which an agent could easily confuse.

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 by the ticker in the name (fetch PEPECOIN pricing), and it clarifies the purchase mechanics ($0.05 USDC on Base or Solana, no account or API key, failed calls not charged). However, it gives no explicit when-to-use or when-not guidance relative to buy_coin_PEPE, buy_crypto_price, or the other buy_tok_* variants.

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