Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ALCH

Paid. Alchemist AI (ALCH) 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/ALCH.

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

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 supplied, the description carries the full burden and does substantial work: it discloses that the call is paid, the exact price and accepted payment chains, that no auth is needed, and that failures are not charged. It omits the response format, latency, and whether fields like market-cap rank can be null, keeping 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Telegraphic but front-loaded: the payment model leads, followed by payload contents, cost, auth, failure policy, and URL. Every element carries information; 'No account, no API key' is mildly redundant and the sentence fragments trade readability for density.

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 paid single-resource fetch with no output schema, the description covers cost, payment rail, auth requirements, failure billing, and the data returned — everything needed to decide and invoke. Only the response shape and edge-case behavior of fields like market-cap rank are left unstated.

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 input schema has zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description still usefully pins the token (ALCH) and the exact endpoint URL, preventing ambiguity about what fixed resource is being fetched.

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 concrete resource and payload: 'Alchemist AI (ALCH) price: live USD price, 24h change and market-cap rank', which is far more specific than the name alone. It does not, however, distinguish itself from the generic sibling buy_crypto_price, so an agent cannot tell from the description whether this is the general price tool or a token-specific paid endpoint.

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?

The description gives purchase context (paid, $0.05 USDC on Base or Solana, no account or API key required, failed calls not charged), which effectively tells the agent when invocation is worthwhile. It never names an alternative such as buy_crypto_price or explains when NOT to buy this endpoint, so the routing guidance is only implied.

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