Skip to main content
Glama

SouthPow crypto & market data

buy_coin_EUL

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses the paid x402-style model, exact price, currency and chain, the no-auth requirement, and that only successful calls are billed. It also names the data provenance (Coinbase Exchange with Kraken cross-check). It omits latency, rate limits, and response format, which keeps it from a 5.

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?

Telegraphic but efficient: cost is front-loaded, then the returned fields, then payment terms, then the endpoint URL. No redundant sentences, though the fragmented phrasing ('Paid.' / 'No account, no API key.') reads tersely rather than flowing.

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 tool, the description supplies the return-value inventory (price, OHLC, % change, volumes) and the full payment/access picture an agent needs before calling. Only the concrete output shape (JSON keys) is left unspecified, a minor gap.

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 to add beyond the schema. The description appropriately spends its words on payment and output fields instead.

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 specific resource (EUL/USD) and enumerates exactly what is returned: last price, 24h open/high/low, % change, and 24h/30d volume. It is unmistakable which token this covers. It does not explicitly contrast itself with the generic sibling buy_crypto_price or the hundreds of other buy_coin_* tools, leaving differentiation to 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 Guidelines4/5

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

States the practical preconditions clearly: costs $0.25 USDC on Base, requires no account or API key, and failed calls are not charged. That covers cost and access context well. It stops short of saying when an agent should prefer this over buy_crypto_price or other price sources, and offers no exclusions.

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