Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ETN

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

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

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 supplied, the description carries the full burden and does substantial work: it discloses that the call is paid, the exact price and accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. That refund/settlement detail is exactly the kind of behavior an agent cannot infer from structured fields. It does not state latency or rate limits, keeping it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short clauses, each earning its place: what you get, what it costs, where to pay, what auth is needed, and the failure policy. 'Paid.' is front-loaded so the agent sees the cost signal before anything else, and the URL is placed last where it does not interrupt the decision-relevant content.

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-annotation, no-output-schema purchase tool, the description covers cost, payment rails, auth requirements, refund policy, and returned fields — nearly everything needed to call it correctly. The only real gap is data freshness/latency expectations for a 'live' price, which an agent paying per call might want.

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 nothing for the description to disambiguate. The endpoint URL is included, which is extra context rather than 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 concrete verb and resource (buy the Electroneum/ETN price feed) and enumerates the returned fields: live USD price, 24h change, market-cap rank. The token is unambiguous, so an agent can distinguish it from the hundreds of buy_tok_* siblings at a glance. It stops short of naming a generalist alternative such as buy_crypto_price, so it is clear but not fully differentiated.

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?

The description makes the trigger condition obvious by implication (you want ETN price data), and the 'Paid... $0.05 USDC' line signals a purchase decision. However, it never says when to prefer this over the generic buy_crypto_price or a coin-listing sibling, and gives no guidance on caching or repeat calls despite a per-call charge.

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