Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_kava

Paid. Kava 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/kava.

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

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, the description does substantial work: it discloses the $0.002 USDC charge, Base or Solana payment options, the lack of account/API-key requirements, and that failed calls are not charged. It also states freshness (“live”) and provenance (“DefiLlama data”), providing strong operational transparency for a simple paid lookup.

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 compact and front-loads the paid nature and exact metric before giving cost, access, failure-billing, and endpoint details. Each short statement supplies useful selection or invocation information without filler.

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 lookup, the scope, source, fee, access requirements, failure billing, and endpoint are sufficient to select and invoke it. Without an output schema, the absence of response units/format and any detail about how payment is authorized remain modest gaps.

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?

There are no inputs whose meanings require clarification, so the zero-parameter baseline applies. The fixed Kava scope and endpoint reinforce that this is a straightforward zero-argument call.

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?

It identifies the exact data product—live Kava DeFi TVL plus 1d/7d/30d changes—and names DefiLlama as the source. This distinguishes it from coin-price and yield siblings, although it is phrased as a noun phrase rather than an explicit “get” or “return” action.

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

Usage Guidelines4/5

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

“Live” TVL and the named change windows establish a clear use case for obtaining current Kava DeFi TVL and recent changes. It does not explicitly route agents to buy_coin_KAVA for token pricing or to other buy_tvl_* tools for other chains, so the guidance is contextual rather than exhaustive.

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