Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_avalanche

Paid. Avalanche total value locked (TVL) in DeFi, live, with 1d/7d/30d change (DefiLlama data). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/defillama/tvl/avalanche.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full load, and it discloses a lot: paid, exact price ($0.002 USDC), accepted payment chains (Base or Solana), no account or API key required, and that failed calls are not charged — all decision-relevant before an agent spends money. It stops short of describing the payment flow and the response shape, which is why it is not a 5.

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 pricing caveat is front-loaded in a single word ('Paid.'), followed by what the data is, the source, the price and payment rails, then the failure policy. Every fragment earns its place; the endpoint URL is the only mildly extraneous item and still aids debugging.

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 paid data endpoint, the description covers cost, payment currency and chains, freshness, source, field content (TVL plus three change windows) and billing on failure. The only missing piece is any hint about the response envelope or how payment authorization is handled at call time.

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; the baseline for a parameterless schema applies. The description correctly avoids inventing argument details and instead spends its words on cost and data content.

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 (Avalanche DeFi total value locked), its freshness (live) and its payload (1d/7d/30d change), plus the upstream source (DefiLlama). Against a sibling list containing dozens of buy_tvl_<chain> tools, the chain qualifier alone makes selection unambiguous.

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 is only implied by the chain name: an agent infers this is the Avalanche variant rather than buy_tvl_ethereum or buy_yields_chain_avalanche. There is no explicit 'use when…' clause, no mention of when a sibling (e.g. the yields tool) would be a better pick, and no prerequisites stated beyond the cost note.

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