Skip to main content
Glama

SouthPow crypto & market data

buy_tok_APEPE

Paid. Ape and Pepe (APEPE) 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/APEPE.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose important traits: it is a paid call ($0.01 USDC on Base or Solana), requires no account or API key, and failed calls are not charged. It omits response format details, latency, idempotency, and whether payment is per-call or per-session, which matters for a paid endpoint.

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-loads 'Paid.' then the data provided, then commercial terms, then the URL — a sensible ordering for an agent deciding whether to spend money. Slightly terse to the point of abruptness, and the raw URL duplicates info the transport already carries, but nothing is wasted.

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, and the description names the returned fields (USD price, 24h change, market-cap rank), so return value is adequately conveyed. Payment mechanics and auth requirements are covered. For a zero-param paid lookup this is close to complete, missing only error/failure semantics beyond the 'not charged' note.

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. No misleading param information is present.

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 what it returns: 'Ape and Pepe (APEPE) price: live USD price, 24h change and market-cap rank.' That is a clear verb-free but unambiguous outcome. It does not explicitly contrast with siblings like buy_crypto_price or buy_coin_APE/PEPE, relying instead on the token name embedded in the tool 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 only implied: the agent infers this is the endpoint for APEPE price data. There is no statement about when to prefer buy_crypto_price or the buy_coin_* variants, and no exclusions. The payment and no-auth notes give context for calling but not for tool selection.

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