Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_vaulta

Paid. Vaulta 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/vaulta.

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

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 at all, the description carries the full burden and does well: it discloses cost, accepted payment rails, absence of auth/account requirements, the failure-charging policy, and the underlying endpoint URL. It stops short of describing the response shape (field names, units, timestamp) for a data-only tool where that would be the remaining unknown.

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-loaded with "Paid." so the cost signal lands first, then purpose, then terms, then URL — a sensible priority order in five short fragments. Dense and nearly waste-free; the trailing URL is the only element that could be considered optional metadata rather than guidance.

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 endpoint, the description covers what an agent needs to decide and call: what data, freshness, change windows, price, payment chains, auth, and failure billing. Only the shape of the returned payload is left unspecified, which is a modest 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?

The tool takes zero parameters (empty properties, empty required), so there is nothing for the description to disambiguate. It correctly avoids inventing arguments and instead makes clear the chain is baked in, which is the only semantic question a caller could have.

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?

"Vaulta total value locked (TVL) in DeFi, live, with 1d/7d/30d change (DefiLlama data)" states the resource, the metric, the granularity and the upstream source in one clause, which cleanly separates it from the ~60 other buy_tvl_<chain> siblings. It is clear but never names a specific sibling or says the chain is fixed by the tool name rather than a parameter.

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?

Payment terms ("$0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged.") give the preconditions for calling, which is real usage guidance. However, there is no explicit when-to-use/when-not guidance — it never says to use a different buy_tvl_<chain> tool for other chains, or to check buy_health_paid before paying.

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