Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_stacks

Paid. Stacks 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/stacks.

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

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 burden and does it well: it discloses that the call is paid, the exact price, accepted payment rails, that no account or API key is needed, and that failed calls are not charged. The main gap is that it only loosely characterizes the returned payload (TVL plus 1d/7d/30d change) with no units or format, and no output schema exists to fill that in.

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?

The definition is compact and front-loads the key facts: what the data is, then price, then access conditions, then provenance. The telegraphic fragments and trailing raw URL are slightly inelegant but each carries information an agent needs before paying.

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 paid data endpoint with no output schema, the description supplies what matters most: data content, source, freshness ('live'), price, payment method, and failure charging policy. Only the exact response shape and units are absent, a minor gap given the simplicity of the call.

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 and the schema is an empty object, so there is nothing for the description to clarify. Baseline 4 applies; the description neither omits nor misrepresents any input.

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 a specific resource and dataset clearly: Stacks TVL in DeFi with 1d/7d/30d change, sourced from DefiLlama. An agent can distinguish it from the per-chain buy_tvl_* and yield siblings by the named chain and metric. It stops short of explicitly contrasting itself with those siblings, but the noun phrase is unambiguous.

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?

There is no explicit when-to-use or when-not guidance against sibling tools such as buy_tvl_* for other chains or buy_yields_chain_stacks. The payment and access conditions ('$0.002 USDC on Base or Solana', 'No account, no API key') imply the context in which it can be invoked, but routing guidance 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