Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_bitcoin

Paid. Bitcoin 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/bitcoin.

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

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 provided, the description carries the full burden and does well: it discloses that the call is paid, the exact price, the accepted payment rails, that no account or API key is needed, and that failed calls are not charged. What is missing is any statement about rate limits, latency, or the shape of the returned payload.

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?

Front-loaded with 'Paid.' so the cost is known before anything else, then the data description, then the terms. Roughly two sentences plus a URL, with no filler or repetition.

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-argument read tool this covers the essentials an agent needs to decide and pay: what data, what time windows, what source, what cost, what rails, and failure billing. The only gap is the return structure, which is not supplied by an output schema and is only partially implied by 'with 1d/7d/30d change'.

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 and there is no parameter meaning for the description to add. The mention of 1d/7d/30d change correctly signals that those windows are returned rather than configurable inputs.

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?

The description names the exact resource and metric ('Bitcoin total value locked (TVL) in DeFi'), the freshness ('live'), and the fields returned ('1d/7d/30d change'), plus the upstream source (DefiLlama). It does not explicitly contrast itself with the many sibling buy_tvl_<chain> tools, though the 'Bitcoin' scope does the distinguishing work implicitly.

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?

It states the commercial and access conditions for calling it ($0.01 USDC on Base or Solana, no account or API key, failed calls not charged), which is genuinely useful before invoking. However, there is no guidance on when to prefer this over a sibling such as buy_tvl_ethereum or a coin-price tool, so usage selection is only implied.

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