Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ALFW

Paid. Alpha Bulgaria Warrants (ALFW) 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/ALFW.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 mostly meets it: it discloses the monetary cost, the accepted payment chains, the absence of auth requirements, and the no-charge-on-failure policy, which is important retry-safety information. It does not cover rate limits, latency, or what an error response looks like.

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?

It opens with the single most decision-relevant word ('Paid') and then packs payload, price, payment rails, auth posture, and endpoint into a few tight fragments. No sentence is filler.

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-argument, single-token price read with no output schema, the definition covers cost, payment, prerequisites, and the fields returned, which is enough to call it correctly. Only the exact response shape and failure modes are left implicit.

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 parameter semantics is baseline 4; there is nothing for the description to disambiguate. The embedded endpoint URL is a useful addition that the empty schema does not convey.

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 a specific resource (Alpha Bulgaria Warrants, ALFW) and the exact payload: live USD price, 24h change, and market-cap rank. The verb is implied by context ('price: live USD price...') rather than stated outright, and it never distinguishes this from broader siblings like buy_crypto_price or the buy_coin_* family, so it is clear but not sibling-differentiated.

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 gives concrete preconditions for invoking: the call is paid at $0.05 USDC on Base or Solana, requires no account or API key, and failed calls are not charged. That is exactly the context an agent needs before deciding to call. It stops short of naming when to prefer this over buy_crypto_price or a buy_coin_* lookup, so there is no explicit alternative routing.

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