Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ALEO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 the payment model, cost and currency, the lack of authentication, the refund policy on failures, and the upstream data sources (Coinbase Exchange with Kraken cross-check). It stops short of noting data staleness, caching, or rate limits, which are relevant for a paid price feed.

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?

The text is front-loaded with the most decision-relevant fact ('Paid.') and then packs coverage, sources, pricing, and auth in a few dense sentences with no filler. The trailing URL is the only element that could be trimmed, but it is compact and useful for verification.

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 price lookup with no output schema, the description supplies enough to act: it lists the returned fields, the exchanges used, the cost, and the endpoint. It lacks the response serialization format and any freshness guarantee, which are the only remaining gaps for a paid data call.

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 there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends no words on inputs and instead invests them in cost and return fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (ALEO/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, and 24h/30d volume. Because each sibling is a distinct token, the ALEO naming plus explicit field list is unambiguous and lets an agent select the right tool without inspecting the schema.

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?

It clearly establishes the preconditions for use: it is a paid call ($0.01 USDC on Base), needs no account or API key, and failed calls are not charged. It does not explicitly compare itself against the general-purpose sibling buy_crypto_price or state when a different price tool would be preferable, so alternative routing is left to inference.

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