Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_hydration

Paid. Hydration 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/hydration.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses that the call is paid, the exact price and accepted payment rails, that no credentials are needed, and that failures are refunded. It does not describe response shape, freshness/latency, or what a payment failure looks like (402 handling), which are the remaining gaps for a paid endpoint.

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?

Dense and front-loaded — the financial cost signal ('Paid') sits first, followed immediately by what the data is, then logistics. Slightly clipped, telegraphic phrasing ('Paid.', 'No account, no API key.'), and the raw URL is marginal value for an MCP caller, but nothing is wasted.

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-param, no-output-schema, unannotated tool, the description supplies the essentials: the metric, the chain, the data source, the change windows, and the payment/auth model. Missing only return-format and error/payment-failure handling details, which is a modest gap given the tool's simplicity.

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 beyond what the empty schema already shows. Baseline 4 applies; the description correctly adds no filler about inputs.

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?

Uses a specific resource ('Hydration total value locked (TVL) in DeFi') plus scope qualifiers ('live, with 1d/7d/30d change') and the upstream source (DefiLlama). The chain name in prose distinguishes it cleanly from the many sibling buy_tvl_* chain endpoints without needing to inspect any schema.

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?

Gives clear operational context: it costs $0.002 USDC on Base or Solana, requires no account or API key, and failed calls are not charged — which tells the agent the preconditions for calling it. It never explicitly names an alternative or a when-not condition (e.g., that buy_tvl_ethereum exists for other chains), so routing relies on the chain name alone.

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