Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_stable

Paid. Stable 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/stable.

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

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, the description carries the full burden and does well: it discloses that calls are paid ($0.002 USDC), accepted on Base or Solana, require no account or API key, and that failed calls are not charged. It omits rate limits, latency, and what the response body looks like, which are the remaining behavioral unknowns for a paid endpoint.

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 the payload ('Stable total value locked... 1d/7d/30d change'), followed by price, payment rails, auth posture, billing policy, and endpoint URL. Every sentence carries a distinct operational fact with no filler.

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 endpoint with no output schema and no annotations, the description supplies the essentials an agent needs to transact correctly: cost, currency, accepted chains, no-auth posture, failure billing, and the metric set returned. Only the exact response shape and any rate/throughput limits are left unstated.

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. It usefully notes that the 1d/7d/30d changes are returned rather than requested, which preempts an agent trying to pass a window argument.

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 metric: DeFi total value locked with 1d/7d/30d change, sourced from DefiLlama. The scope qualifier 'Stable' is ambiguous in prose (it reads like an adjective describing the metric, but it is the chain name given siblings such as buy_tvl_ethereum and buy_tvl_solana), so the description never explicitly says 'TVL for the Stable chain' or points at a sibling for contrast.

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 context is implied by the data described (live DeFi TVL with 1d/7d/30d deltas), but there is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives like buy_tvl_ethereum for another chain or buy_yields_chain_stable for yield data. The payment instructions tell the agent how to transact, not when this tool is the right 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