Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_aptos

Paid. Aptos 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/aptos.

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

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 at all, the description carries the full burden and does well: it discloses that the call is paid, the exact price and payment rails, that no auth is required, and that failed calls are not charged. The gaps are rate limits, latency, and result units (USD?), but the billing and access profile is unusually well covered for an annotation-free tool.

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?

Every clause earns its place: purpose, metric windows, data source, price, payment chains, auth requirement, failure billing, and endpoint URL, all front-loaded with 'Paid.' so the cost is the first thing seen. No filler or redundancy.

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-argument, no-annotation tool with no output schema, the description covers enough to call it confidently: what data returns (TVL plus 1d/7d/30d change), what it costs, and how to pay. Minor gaps remain around response shape/units and rate limits, which matter more because no output schema exists.

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, and the baseline of 4 applies. The description correctly implies the call is fully fixed (chain and metrics baked in) rather than leaving the agent hunting for filters.

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 pinpoints a concrete resource: Aptos DeFi total value locked, live, with 1d/7d/30d change, sourced from DefiLlama. The verb is implicit (the 'buy_' prefix plus 'Paid' signals a purchase-and-fetch), but the resource is unambiguous. It does not explicitly contrast with the many sibling buy_tvl_* chains, though the chain-specific wording does that implicitly.

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?

It tells the agent the cost basis ($0.005 USDC), chains for payment, and that no account/API key is needed, which are useful preconditions for deciding to call. However, it gives no explicit when-to-use or when-not guidance, and never distinguishes itself from adjacent siblings like buy_yields_chain_aptos or buy_tvl_ethereum beyond the chain name.

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