Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_ethereum

Paid. Ethereum 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/ethereum.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations present, the description carries the full behavioral burden and does substantial work: it declares the tool is paid, the exact price ($0.002 USDC), the accepted payment chains (Base or Solana), the no-credential access model, and the refund policy for failed calls. What it omits is rate limiting and any sense of response shape or latency beyond 'live'.

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?

Front-loads the payment flag, then the purpose, then access and pricing terms, then the endpoint URL — a sensible order with no filler sentences. The delivery is telegraphic and slightly list-like rather than flowing prose, but every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 purchase tool, the description covers everything that could block a successful call: what data is returned, that it costs money, how to pay, that no credentials are needed, and that failures are not billed. Safety annotations are absent but irrelevant here since the operation is a trivial read-purchase with no destructive surface.

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, which is the baseline-4 case; there is nothing the description could add that the empty schema does not already settle. The chain scope is fixed by the tool name rather than a parameter, and the description correctly implies no filtering options exist.

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?

States a specific resource (Ethereum DeFi total value locked), a specific data shape (live with 1d/7d/30d change), and the underlying source (DefiLlama). Combined with the chain-specific tool name, an agent can distinguish it from the other buy_tvl_* siblings without opening anything.

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 context for when this applies — Ethereum-only DeFi TVL, live series with three change windows — and pre-empts the access questions an agent would otherwise have to guess at (no account, no API key). It does not spell out a when-not or point at a sibling such as buy_tvl_solana, so it stops short of full routing guidance.

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