Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_monad

Paid. Monad 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/monad.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 cost ($0.002 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — all material behavior beyond the schema. It stops short of return shape detail, rate limits, or latency.

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 two things that gate the call (paid, what it returns), then cost, auth, billing, and endpoint in short clauses. No filler sentences; every fragment carries a distinct fact.

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 parameterless paid endpoint with no annotations and no output schema, the description supplies the metric content (TVL plus 1d/7d/30d change), provenance, price, payment rails, and billing policy — enough to decide and invoke. It only lacks an indication of response structure or freshness guarantees beyond 'live'.

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 there is nothing to disambiguate; baseline 4 applies. The description correctly implies a parameterless call by naming a fixed chain and fixed metric set.

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?

States a specific resource and scope: Monad DeFi TVL, live, with 1d/7d/30d change, sourced from DefiLlama. An agent can distinguish this from the many buy_tvl_<other-chain> siblings and from buy_yields_chain_monad without opening any schema.

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?

The leading 'Paid' plus the explicit price signals that this is a cost-incurring call to be used only when the data is actually needed, which is implicit usage guidance. However, it never states when to prefer this over a sibling (e.g. a free source, or buy_yields_chain_monad) or any exclusions.

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