Skip to main content
Glama

SouthPow crypto & market data

buy_coin_AVT

Paid. AVT/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.10 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/AVT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Since no annotations were provided, the description carries the full behavioral burden, which it fulfills exceptionally well. It explicitly states the cost, the payment chain (Base), the data sources (Coinbase/Kraken cross-check), and operational risk (failed calls not charged).

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?

The description is highly dense and front-loaded with the most critical information (Asset, Payment status, Data). There is no redundant language; every element serves a clear purpose for the AI agent or the end-user.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is highly complex in terms of external operations (payment, specific API/URL, data sourcing). Despite having no parameters, the description is maximally complete by detailing the financial, technical, and functional boundaries of the tool.

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?

With zero parameters, the description must compensate by providing context about the data being returned. It clearly enumerates the metrics provided (last price, open/high/low, % change, volume), adding significant semantic value to the empty input schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches live pricing and specific historical metrics (24h stats, volume) for the AVT/USD asset. By naming the specific coin, it differentiates itself from the extensive list of other sibling `buy_coin_` tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides crucial usage constraints that act as usage guidelines: it is 'Paid' ($0.10 USDC on Base), requires no account/API key, and specifies that failed calls are not charged. This helps the agent determine if using this tool is viable before invocation.

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