Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_hedera

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the call is paid ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It stops short of explaining how payment is actually executed and what a paid-call response envelope looks like.

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?

Two dense sentences plus the endpoint URL, with the paid/cost constraint front-loaded before the data description. Every clause carries information an agent needs (price, payment rails, billing on failure, data source, metrics).

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 endpoint, the definition covers what is returned (TVL plus 1d/7d/30d change) and the commercial terms, which is most of what an agent needs before calling. The remaining gap is the payment mechanics (how the $0.01 is settled and whether a retry after payment failure is safe).

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 applies. The description instead spends its words on cost and scope, which is the right allocation.

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?

"Hedera total value locked (TVL) in DeFi, live, with 1d/7d/30d change (DefiLlama data)" names the exact resource, the metrics returned, and the upstream source, which separates it from the other buy_tvl_* siblings by chain. The only weakness is that the action itself (buy a paid data fetch) is conveyed by the word "Paid" and the price rather than an explicit verb.

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 context is implied: an agent can infer this is the tool for Hedera chain TVL. There is no explicit when-to-use/when-not, and no routing statement such as "for other chains use buy_tvl_ethereum / buy_tvl_solana", even though dozens of near-identical siblings exist and a routing hint would be cheap.

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