Skip to main content
Glama

SouthPow crypto & market data

buy_coin_AVNT

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

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

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 well: it discloses the payment amount and chain ($0.05 USDC on Base), the absence of auth requirements, and the favorable failure policy (failed calls not charged). It does not cover rate limits, idempotency, or the response format/schema. The payment and billing details are the material facts here and they are stated up front.

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?

Roughly three dense sentences: paid notice first, then the data payload, then cost/access terms, then the endpoint URL. Every clause adds information and the price/access terms are not buried. The telegraphic 'Paid.' fragment and abbreviation-heavy style are slightly terse but not wasteful.

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, no-output-schema price endpoint, the description supplies enough to call it correctly: the exact URL, the fixed asset pair, the cost, and the fields returned. The returned field list partially substitutes for a missing output schema. It does not state the response encoding (JSON?) or freshness/update cadence, which would fully close the gap.

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 reflects the no-argument nature by implying a single fixed endpoint URL for the AVNT pair. Nothing in the text misleads about inputs.

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 (AVNT/USD live data) and enumerates exactly what comes back: last price, 24h open/high/low, % change, 24h and 30d volume. The ticker in the tool name distinguishes it from the ~300 sibling buy_coin_* tools without needing to restate that. It is a noun-phrase fragment rather than a verb statement of what the tool does, which keeps it just short of a 5.

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?

Practical entry conditions are stated clearly – $0.05 USDC on Base, no account or API key, failed calls not charged – so an agent knows the prerequisites and risk profile before calling. However, it gives no guidance on when to prefer this over the related sibling buy_crypto_price, or whether to use it versus a different ticker tool. Usage context is implied by the ticker, not explained.

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