Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_rise

Paid. RISE 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/rise.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description supplies substantial operational detail: a $0.005 USDC charge, payment on Base or Solana, no account or API key, and no charge for failed calls. 'Live' and the DefiLlama attribution also set freshness and provenance expectations, although the exact payment flow and any rate limits remain unspecified.

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?

The short, front-loaded description covers scope, metric windows, source, price, payment networks, authentication needs, failure billing, and endpoint in compact statements. There is no substantive filler or repetition beyond the useful general 'Paid' flag followed by exact pricing.

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 simple no-argument lookup, this covers nearly everything needed to select and invoke it, including cost and failure behavior. Because there is no output schema, the absence of response-field details and an explicit TVL unit or currency leaves a small but real gap in interpreting results.

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?

There are no input parameters, so the zero-parameter baseline applies and there is no argument syntax to explain. The description usefully confirms the fixed RISE scope and concrete endpoint, preventing any expectation of a chain or date-range 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 identifies a fixed-scope lookup of RISE's live DeFi TVL and its 1d/7d/30d changes, sourced from DefiLlama. This distinguishes it from other buy_tvl_* chains and from coin-price and yield siblings, while clarifying that 'buy' refers to paying for data rather than purchasing RISE.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear use case: choose this tool when current RISE TVL and those three change windows are needed. It does not explicitly route other chains to their buy_tvl_* siblings or state when not to use it, so the guidance is contextual rather than exhaustive.

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