Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ALCX

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the full burden and does well: it discloses the payment requirement, exact price and chain, absence of auth, the no-charge-on-failure policy, and the upstream data sources (Coinbase Exchange with Kraken cross-check). It stops short of stating rate limits, latency/freshness guarantees beyond 'live', or retry/error behavior.

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?

Front-loaded with the most decision-relevant fact ('Paid.') and then the payload, price, prerequisites, and endpoint. The terse fragment style is dense but every clause carries information; only the bare URL is slightly raw, though it is operationally useful for a paid endpoint.

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-output-schema tool, the description compensates by enumerating exactly which price fields are returned and which exchanges feed them. Payment and access prerequisites are covered; what remains unaddressed is failure/error shape and refresh cadence.

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 schema semantics to add; the baseline of 4 applies. The description correctly implies no caller-supplied inputs are required.

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 resource and scope: live ALCX/USD price with an explicit field list (last, 24h open/high/low, % change, 24h and 30d volume). The ticker in the name plus the pair in the description lets an agent distinguish it from the many buy_coin_<TICKER> siblings without opening 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?

Gives clear operating context: it is a paid call, costs $0.002 USDC on Base, requires no account or API key, and failed calls are not charged. It does not explicitly route between this and generic siblings like buy_crypto_price, so the when-to-use-vs-alternative guidance is implied by the ticker 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