Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ALUSD

Paid. Alchemix USD (ALUSD) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/ALUSD.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does a good job disclosing the commercial terms: $0.05 USDC on Base or Solana, no account or API key required, and failed calls are not charged. It does not cover response shape details beyond the three named fields, nor latency or rate-limit behavior, so the operational picture is only partially complete.

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?

Three compact sentences with no filler; the 'Paid.' prefix and the price/cost/URL ordering are front-loaded with the most decision-relevant facts. The URL at the end is somewhat raw but still earns its place as the endpoint reference.

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 price tool, the definition covers what is returned, what it costs, how to pay, and that failures are free. The main residual gap is the exact response structure and freshness of the quote, which an agent might want before paying.

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 nothing for the description to disambiguate; the baseline applies. The description correctly signals that no arguments are needed by binding the asset in the tool name and URL.

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 exact resource (Alchemix USD / ALUSD) and the specific fields returned: live USD price, 24h change, and market-cap rank. It is clearly a single-asset price lookup, though it never explicitly distinguishes itself from the large buy_tok_* family or from buy_crypto_price, leaving the agent to infer that the asset is pre-bound by the tool name.

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 rather than stated: an agent can infer 'call this when you need ALUSD price data'. There is no explicit when-not guidance and no pointer to alternatives such as buy_crypto_price for arbitrary assets, which matters given hundreds of near-identical siblings.

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