Skip to main content
Glama

SouthPow crypto & market data

buy_coin_AAVE

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so well: it discloses the cost and payment rail ($0.25 USDC on Base), the authentication model (no account, no API key), the failure billing policy (failed calls not charged), and the upstream data provenance (Coinbase Exchange with Kraken cross-check). These are exactly the behavioral facts an agent needs before spending money on a call, and they go well beyond restating the tool name.

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?

The description is dense and front-loaded: asset and data fields come first, then price and payment terms, then the endpoint URL. The telegraphic style ("Paid.", "$0.25 USDC on Base.") is efficient but slightly fragmented, and the trailing raw URL is weakly integrated into the flow.

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, single-purpose paid endpoint, the description covers what an agent needs to decide and act: what data comes back, what it costs, how billing fails, and where to send the request. Without an output schema the exact response shape (field names, units, JSON structure) is only described in prose, which leaves a minor gap but nothing blocking.

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 and the baseline of 4 applies. The description correctly signals that the asset is fixed by the endpoint rather than passed as an argument, which prevents an agent from hunting for a symbol parameter.

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 names the exact resource (AAVE/USD spot data) and enumerates the specific fields returned: last price, 24h open/high/low, % change, and 24h/30d volume. The coin symbol in the tool name plus the explicit pair makes it trivially distinguishable from the ~400 sibling per-coin tools, which are identical except for the asset.

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?

The paid nature and the $0.25 USDC-on-Base cost imply this is a metered data call to be used deliberately, and the "failed calls not charged" note reduces hesitation. However, there is no explicit when-to-use statement and no routing advice relative to siblings like buy_crypto_price (generic) or other buy_coin_* tools, so the agent must infer that this is the AAVE-specific endpoint rather than the general one.

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