Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_base

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 behavioral burden and does substantial work: it discloses the paid model ($0.005 USDC), both accepted payment rails (Base or Solana), the absence of account/API-key requirements, and that failed calls are not charged — the last being meaningful retry-safety context. It does not describe response shape or latency, but for a zero-parameter read this is well above adequate.

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-loaded with the billing flag ('Paid.') then the resource definition, followed by cost, payment rails, auth requirements, and endpoint URL — a sensible decision-order for an agent. Every sentence is short and earns its place, though the raw URL at the end is somewhat unexplained.

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?

No output schema exists, so the description must convey what comes back; it does so by naming the metric and the 1d/7d/30d change components. Combined with pricing, payment options, and no-auth disclosure, an agent has nearly everything needed to decide and invoke. The only gap is the exact response format.

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 and the baseline of 4 applies. The description correctly avoids inventing parameters and instead spends its words on cost and access conditions.

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?

States the specific resource precisely: Base-chain DeFi TVL, live, with 1d/7d/30d change and DefiLlama as the source. The chain scoping ('Base') is what separates it from the many buy_tvl_* siblings, and that distinction is stated rather than implied. It falls short of a 5 only because the acquiring verb ('buy') is left to the tool name rather than stated in the description.

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 is implied by the resource name (call this when you need Base TVL, not Ethereum or Solana TVL), and the price line gives a decision-relevant cost signal. However, there is no explicit routing guidance naming alternatives such as buy_tvl_ethereum or buy_yields_chain_base, and no statement of when this is the wrong choice.

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