Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_op-mainnet

Paid. OP Mainnet 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/op-mainnet.

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_op-mainnet"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose cost, payment rails, no-auth access, and the important detail that failed calls are not charged, which is genuinely useful billing behavior. But it says nothing about freshness guarantees, rate limits, or what a caller receives (structure, units, timestamps), leaving most invocation-relevant behavior undisclosed.

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 paid flag, then the data content, then price/access terms, then the URL — a sensible order with no filler. The telegraphic phrasing ('Paid.', '$0.002 USDC on Base or Solana') is dense but readable.

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 paid data endpoint, the description covers what data comes back, the source, the price, payment networks, auth requirements, and failure billing. The main gap is the exact response shape and units, which the caller must discover by invoking.

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 no parameter semantics to explain; the baseline for a no-parameter tool applies. The description appropriately spends its text on output content and payment mechanics instead.

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 the specific resource and scope: OP Mainnet DeFi total value locked, live, with 1d/7d/30d change from DefiLlama. That cleanly separates it from the other chain-specific buy_tvl_* siblings through the chain name, though it never explicitly contrasts itself with related tools such as buy_yields_chain_op-mainnet.

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?

Gives purchase context (paid, $0.002 USDC on Base or Solana, no account or API key) but no explicit guidance on when to pick this over a sibling, e.g. a yields or per-protocol tool for the same chain. Usage is implied by the chain name rather than stated.

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