Skip to main content
Glama

SouthPow crypto & market data

buy_coin_EGLD

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With zero annotations the description carries the full behavioral burden and does a good job: it discloses the paid model and exact price ($0.10 USDC on Base), that no account or API key is required, that failed calls are not charged, the upstream data sources (Coinbase Exchange with Kraken cross-check), and the raw endpoint URL. What is missing is a note on payment mechanics (how the agent settles, e.g. a 402 flow) and any latency/rate-limit behavior.

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?

Very dense and front-loaded: cost and access caveat, then the data payload, then payment terms, then the endpoint. The fragment 'Paid.' at the start is telegraphic but signals the commercial gating early; nothing is filler, though a slightly more connected sentence structure would read better.

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, yet the description effectively serves as one by listing the exact returned metrics, and it covers the commercial and access prerequisites that an agent must know before invoking a paid endpoint. It falls short only on the mechanics of actually paying and on error/failure behavior beyond the no-charge guarantee.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly makes no parameter claims, avoiding confusion about symbol or currency inputs.

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?

Names the concrete resource (EGLD/USD live price) and enumerates exactly the fields returned (last, 24h open/high/low, % change, 24h and 30d volume), so the agent knows precisely what data comes back. It does not explicitly route to alternatives such as the generic buy_crypto_price sibling, but the coin-specific scope is unambiguous from the text itself.

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: 'EGLD/USD live' plus the coin name tells the agent to reach for this when it needs EGLD pricing. There is no explicit 'use this instead of buy_crypto_price' or 'do not use for other coins' guidance, which matters given hundreds of near-identical sibling tools.

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