Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ALEPH

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

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

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, the description carries the full burden and does well: it discloses cost, payment rail (USDC on Base), no-auth access, failure billing policy, data provenance (Coinbase Exchange with Kraken cross-check), and the endpoint URL. It omits rate limits, latency/staleness, and how payment is actually presented at call time, which keeps it short of 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?

Six short fragments, front-loaded with the decision-critical fact 'Paid', then the dataset, then price and access terms. Almost nothing could be removed without losing information an agent needs before spending money.

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 or annotations exist, so the description must describe the payload and economics, which it does by enumerating returned fields and the billing model. It still lacks the response envelope format and the exact payment handshake, the remaining pieces an agent would want for a paid endpoint.

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 no parameters, so the baseline is 4 and there is no schema semantics to compensate for. The description correctly implies a parameterless call and adds the endpoint URL an agent may need.

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?

States a specific asset and dataset: 'ALEPH/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', plus the upstream sources. Combined with the ticker-scoped name, an agent can tell exactly which of the many buy_coin_* siblings to call and what it will get.

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?

Gives clear preconditions for use: it is paid, costs $0.05 USDC on Base, needs no account or API key, and failed calls are free. That is enough to decide whether to call it. It does not, however, point to alternatives such as the generic buy_crypto_price sibling or say when a cross-checked live quote is preferable to a cheaper source.

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