Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_anubis

Paid. Anubis 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/anubis.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 disclosure burden and does well: it declares the tool is paid, the exact price and accepted payment chains, that no authentication is needed, that failed calls are not charged, and that the data is live with 1d/7d/30d deltas. It stops short of explaining the payment mechanics (how the $0.005 is actually settled), rate limits, or response shape.

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-loads the single most decision-relevant fact ('Paid'), then the data contents, then cost/payment rails, then the endpoint URL. Every clause earns its place and there is no padding.

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, the description covers cost, payment chains, auth-free access, failure billing policy, and the returned metrics (TVL plus 1d/7d/30d change), so an agent knows what it gets. The remaining gap is operational: how payment is initiated at call time, which an agent spending money would want spelled out.

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 nothing for the description to disambiguate; the baseline applies. Nothing in the description misleads about inputs.

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 a specific resource and scope: 'Anubis total value locked (TVL) in DeFi' with 1d/7d/30d change, and names the data source (DefiLlama). The chain name implicitly separates it from the many sibling buy_tvl_<chain> tools, though the description never explicitly says 'use this for Anubis rather than the other chain TVL tools'.

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?

Provides real prerequisites: paid, $0.005 USDC on Base or Solana, no account/API key, failed calls not charged. What it does not provide is when to pick this over alternatives (e.g., a general DeFi TVL tool or another chain), and no exclusion or comparison guidance.

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