Skip to main content
Glama

SouthPow crypto & market data

buy_tok_AWIN

Paid. AlphaWin (AWIN) 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/AWIN.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 the cost ($0.05 USDC), accepted payment chains (Base or Solana), absence of auth requirements, and the refund policy ('Failed calls not charged'), plus the underlying endpoint URL. That is exactly the behavioral context an agent needs before spending money. It stops short of describing response format or latency/rate limits.

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?

Front-loaded with 'Paid.' so the cost implication is the first thing the agent sees, followed by payload, price, rails, and guarantees. Every clause adds a distinct operational fact and there is no 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 paid fetch with no output schema, the description covers cost, payment rails, auth, failure billing, and the exact fields returned, which is nearly everything needed to call it. The only gap is that it does not describe the response shape (e.g., JSON structure or units of the 24h change), though the field list largely substitutes for that.

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, which is the baseline-4 case; the description correctly offers no parameter detail because there is nothing to parameterize. The token is baked into the endpoint URL, which the description makes explicit, so no ambiguity remains about how to target AlphaWin.

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 specific resource and the exact payload it returns: 'AlphaWin (AWIN) price: live USD price, 24h change and market-cap rank.' An agent can tell what data comes back. It does not, however, differentiate itself from related siblings such as buy_crypto_price or the buy_coin_* family, so the 'tok' vs 'coin' distinction is left to inference.

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 context is implied by the payment terms ($0.05 USDC, no account, no API key), which tells the agent this is a pay-per-call endpoint with no setup. There is no explicit statement of when to prefer this over a generic price sibling, and no exclusions or prerequisites beyond the payment mechanics.

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