Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_thorchain

Paid. THORChain 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/thorchain.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden, and it does disclose the commercial model well: $0.002 USDC on Base or Solana, no account or API key, failed calls not charged, and live DefiLlama sourcing. It stops short of behavior an agent needs before calling, e.g. response shape, units, latency, rate limits, or whether the 1d/7d/30d values are always present.

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?

'Paid' is front-loaded, followed by data contents, price, and access terms, so the reader gets the important constraints early. The raw endpoint URL at the end is of marginal value to a model and makes the sentence a bit list-like, but overall there is little waste.

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-param paid data fetch with no output schema and no annotations, the description covers the essentials: what data, freshness, source, cost, payment rails, and failure billing. The main remaining gap is the return value's structure and units, which matters because there is no output schema to fall back on.

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 the baseline of 4 applies and there is nothing for the description to clarify. The chain target is baked into the tool name rather than a param, which is consistent.

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?

The description names the exact resource and scope: THORChain TVL from DeFiLlama with 1d/7d/30d change, live. That is specific enough to separate it from buy_tvl_ethereum or buy_tvl_solana without opening a schema. The action verb is only implied by 'Paid' rather than stated, which keeps it just short of a 5.

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 is implied: call this when you need the THORChain chain-level TVL figure. There is no explicit when-to-use vs sibling guidance, and no note on whether buy_cp_defi or buy_yields_chain_* would be a better fit for related DeFi questions. The payment prerequisites are stated, but selection guidance is not.

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