Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_algorand

Paid. Algorand 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/algorand.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 the payment model, price, accepted rails, the no-account/no-key requirement, and the important failure policy that failed calls are free. It stops short of describing payment mechanics (how the $0.01 is actually settled, e.g. x402 handshake), 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the critical fact (Paid) and packs price, rails, auth model, failure policy, source and endpoint URL into a few dense fragments with no filler. The telegraphic style is slightly clipped but every clause earns its place.

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, no-annotation, no-output-schema tool, the description supplies what an agent needs to decide and call: what data comes back (TVL plus 1d/7d/30d change), the source, the cost, and the endpoint. Only the exact response shape and payment flow remain unspecified.

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 the baseline is 4. The description implicitly confirms this by presenting the call as fully parameterless — the only variable is which network you pay on.

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?

Names a precise resource and scope: Algorand DeFi TVL, live, with 1d/7d/30d change from DefiLlama. The chain-specific naming makes it distinguishable from the many sibling buy_tvl_* endpoints 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an agent the practical selection context: it is a paid call at $0.01 USDC on Base or Solana, needs no account or API key, and failed calls are not charged. It does not state when to prefer a non-TVL alternative (e.g. buy_yields_chain_* or buy_stable_*), so no explicit 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