Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_hyperliquid-l1

Paid. Hyperliquid L1 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/hyperliquid-l1.

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_hyperliquid-l1"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a good job: it discloses that the call is paid ($0.002 USDC on Base or Solana), requires no authentication, and that failed calls are not charged. It does not mention rate limits, caching/freshness lag of the 'live' figure, or error behavior beyond the billing policy.

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?

Terse, front-loaded fragments: pricing and access terms are stated immediately after the data description, with the endpoint URL last. Every clause carries information; the raw endpoint URL is the least essential element but is defensible for a paid HTTP API.

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 tool, the description covers what is returned (TVL plus 1d/7d/30d change), the source, the cost and payment rails, and failure billing. Only marginal gaps remain: the exact response shape and data refresh cadence, which are not strictly necessary to call it correctly.

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 the baseline is 4. No parameter meaning is needed, and the description correctly spends its words on output content and access terms instead.

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 (Hyperliquid L1 total value locked in DeFi), states freshness ('live'), and enumerates the fields returned (1d/7d/30d change) plus the data source (DefiLlama). Against a sibling set of hundreds of buy_tvl_<chain> tools, the chain is pinned explicitly, so an agent can select it without ambiguity.

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?

Access conditions are well covered (paid, no account, no API key), which helps an agent decide it *can* call it, but there is no explicit guidance on when to prefer this over alternatives such as buy_yields_chain_hyperliquid-l1 or other chain TVL tools, and no exclusions. Usage is implied by the tool name and scope rather than stated.

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