Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_linea

Paid. Linea 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/linea.

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

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?

No annotations are supplied, so the description carries the whole behavioral burden and it does comparatively well: it discloses the cost ($0.005 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It does not cover rate limits, latency, or response shape, keeping it short of a 5.

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 "Paid." and then packed with what, cadence of change metrics, source, price, payment rails, billing policy, and endpoint. Every clause carries information, though the raw URL is the one element an agent arguably does not need inline.

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 data purchase, the essentials an agent needs before spending money are present: what data, what granularity of change, what it costs, how it is billed, and how it is authenticated (not at all). Return-value granularity (metric field names, timestamp format) is the remaining gap, which is modest for a simple scalar-style metric feed.

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 schema takes zero parameters, so the baseline is 4 and there is nothing for the description to clarify beyond confirming the call needs no inputs. It does that implicitly by never referencing any argument.

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 a specific resource and scope: Linea's DeFi TVL, live, with 1d/7d/30d change from DefiLlama. That is enough to distinguish it from the buy_tvl_* sibling family (each is another chain's TVL) and from buy_yields_chain_linea, which is a different data product.

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?

The word "Paid" plus the price telegraphs that this is a paid per-call lookup and not a free utility, which implicitly frames when to call it. However, it never states when to prefer this over an alternative (for example the free-ish buy_crypto_price, or the yields sibling) or any exclusion, so the routing is left to inference.

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