Skip to main content
Glama

SouthPow crypto & market data

buy_tok_WALLET

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

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

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?

No annotations exist, so the description carries the full behavioral burden and does well: it discloses the price ($0.01 USDC), accepted payment chains (Base or Solana), no-account/no-API-key access, and that failed calls are not charged. What it omits is rate limits, latency, or what a payment failure 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.

Conciseness4/5

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

Compact and front-loaded: what it returns comes first, then cost, then access terms, then URL. Every clause carries information, though the bare URL at the end reads as an implementation detail rather than agent-relevant guidance.

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 data endpoint with no output schema, the description covers the essentials: the returned fields are enumerated, payment and access terms are stated, and charging behavior on failure is clarified. Only absence of response shape/format detail keeps it short of full completeness.

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; baseline 4 applies. The description correctly adds no parameter noise.

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 (Ambire Wallet / WALLET) and the exact payload: live USD price, 24h change, market-cap rank. Clearly distinguishable from sibling feeds by ticker. Slightly weakened by the 'buy_' naming, which suggests a purchase rather than a read, but the description resolves that immediately.

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?

Implied usage is clear: call it when you need WALLET's spot price and market stats. It also flags that the call is paid, which shapes willingness to invoke. However, it never tells the agent when NOT to use it or points to alternatives like buy_crypto_price or the broader buy_coin_* family.

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