Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_rootstock

Paid. Rootstock 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/rootstock.

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

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, the description does real work: it discloses that the call is paid, the exact price ($0.01 USDC), accepted payment rails (Base or Solana), that no account or API key is needed, and that failed calls are not charged. What it does not cover is latency/caching behavior, rate limits, or error semantics beyond 'failed calls not charged'.

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-loads the most decision-relevant token ('Paid') and then packs resource, payload, source, price, and rails into very few words. The trailing raw URL is arguably redundant given the tool identity, but it is one short clause and useful for direct-call fallback.

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 purchase tool, the description covers what is returned (TVL with 1d/7d/30d deltas), where the data comes from, and the full cost/payment model — everything an agent needs before spending money. Only the exact response field layout is unstated, which is a minor gap.

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?

Zero parameters, so the baseline is 4. The description adds no parameter information, and none is needed — the chain is baked into the tool identity.

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?

Names the exact resource ('Rootstock total value locked (TVL) in DeFi') and the payload shape ('live, with 1d/7d/30d change'), plus the upstream source (DefiLlama). This cleanly separates it from the many buy_tvl_<other-chain> siblings by chain specificity, though the description never explicitly contrasts itself with them.

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?

Implicit usage only: an agent can infer it should call this when it needs Rootstock DeFi TVL data. There is no explicit when-not guidance and no mention of the related buy_yields_chain_rootstock sibling that might be the better choice for yield-level detail.

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