Skip to main content
Glama

SouthPow crypto & market data

buy_tok_EGL1

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 burden and does disclose real behavioral traits: it is a paid call ($0.05 USDC on Base or Solana), needs no account or API key, and failed calls are not charged. That is genuinely useful spend/safety context. It still omits rate limits, latency, and whether the endpoint is idempotent or cached, which matter for a metered call.

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.' so cost is the first thing an agent sees, then gives purpose, price, access terms, failure policy, and URL in a compact run of sentences. No filler, though the pricing/access sentences could be consolidated slightly.

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, no-output-schema price endpoint, the description covers what is returned (price, 24h change, market-cap rank), what it costs, and how to access it — enough to call correctly. Return shape (JSON keys, currency precision) is unspecified, which is a minor gap given no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, which normally sets a baseline of 4, but the endpoint encodes the asset in the URL path and the description does not explain that this URL is fixed to EGL1 or whether the same URL pattern generalizes to other tokens. The meaning added over an empty schema is minimal, so 3 reflects the lack of added semantic guidance rather than a gap in parameter documentation.

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-resource pair with scope: 'EGL1 (EGL1) price: live USD price, 24h change and market-cap rank' tells an agent exactly what data comes back. It does not differentiate itself from the sibling families buy_coin_* or buy_crypto_price, so an agent choosing between overlapping price tools gets no routing help, but the purpose itself is unambiguous.

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?

The description explains payment mechanics but never says when to pick this over buy_crypto_price, buy_coin_* or the broader market tools in the sibling list. There are no exclusions or prerequisites beyond the implicit 'use this for EGL1 specifically,' which the name already conveys.

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