Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ELA

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

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

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 no annotations, the description carries the full burden and does well: it discloses the price ($0.002 USDC on Base), that no account or API key is required, that failed calls are not charged, the upstream venues, and the endpoint URL. It omits rate limits, data freshness/latency, and the payment mechanics (how USDC is collected), which keeps it out of the top band.

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?

Roughly four short clauses with no filler; cost and access constraints are front-loaded, then the payload, then the endpoint. The one-word 'Paid.' opener is slightly clipped but functional rather than wasteful.

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, so the description must describe return values, and it does list the metric set and the 24h/30d volume windows. It also covers cost, auth, failure billing, and endpoint. Missing pieces are operational: response format, freshness, and error behavior.

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?

Zero parameters, so the baseline is 4. The description instead spends its words enumerating the returned fields and their sources, which is the useful semantic content for a no-arg tool.

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 resource and payload: 'ELA/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', plus data sources (Coinbase Exchange, Kraken cross-check). Sibling differentiation is only implicit via the ticker embedded in the name; it never says 'use this for ELA rather than other assets', and the 'buy_coin_' prefix could mislead an agent into expecting a trade rather than a paid data fetch.

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 implied (call it when you need ELA/USD spot and 24h stats) but there is no explicit when-to-use or when-not-to-use statement, no mention of how it relates to siblings like buy_crypto_price, and no guidance on caching or how often to pay for a fresh quote.

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