Skip to main content
Glama

SouthPow crypto & market data

buy_coin_EIGEN

Paid. EIGEN/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/EIGEN.

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

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 a solid job: it discloses that the call is paid, the exact price and payment rail, that no authentication is needed, that failed calls are not charged, and the upstream data sources including a Kraken cross-check. It stops short of describing response latency, retry/refund mechanics, or the payment flow itself.

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?

Extremely front-loaded: 'Paid.' flags the critical constraint in one word, then the data payload, then cost, then access terms, then endpoint. No sentence is redundant and nothing important is buried.

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 tool with no output schema, the description does the necessary work by enumerating the returned fields and the sources, so an agent knows what it is buying. The one remaining gap is that it does not specify the response format or the freshness/cadence of the quotes.

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. The description correctly implies the asset is baked into the endpoint (URL includes /price/EIGEN), which confirms no parameterization is needed.

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 the specific resource (EIGEN/USD live price) and enumerates the exact fields returned: last price, 24h open/high/low, % change, 24h and 30d volume. It is clearly distinct from the sibling families (buy_hn_*, buy_pm_*, buy_insider_*), though it never states that the other buy_coin_* siblings cover different assets, leaving that inference to the naming convention.

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?

It conveys the preconditions for calling (no account, no API key, $0.25 USDC on Base) which is real usage context, but it never says when to prefer this over buy_crypto_price or another coin-specific tool, nor when not to use it. The usage guidance is implied by the tool name rather than stated.

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