Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_stellar

Paid. Stellar 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/stellar.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 so well: it discloses the paid model ($0.01 USDC), the accepted chains for payment (Base or Solana), no account or API key requirement, and that failed calls are not charged. It stops short of saying whether pricing is per call or per payload and what a partial or errored response looks like.

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' and the data scope, then payment mechanics, then the endpoint URL. Every sentence carries information, though the raw URL at the end is the least valuable element and could have been omitted.

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?

No output schema exists, so the description must hint at returns: it names TVL plus 1d/7d/30d change and the DefiLlama provenance, which is enough to set expectations. Payment and authentication behavior are also covered, leaving only response envelope details unstated.

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?

Zero parameters, so the baseline of 4 applies. There is nothing for the description to disambiguate, and the request shape is implicitly a bare call with no inputs.

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?

States the exact resource (Stellar DeFi TVL), the data source (DefiLlama), and what comes back (live TVL plus 1d/7d/30d change). The chain name in the text and the tool name together separate it from the many sibling buy_tvl_* tools without needing the schema.

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?

Usage is implied by the resource name: fetch Stellar TVL when Stellar is the chain of interest. However, it never routes the agent explicitly, e.g. no note that siblings cover other chains, nor when to prefer this over buy_yields_chain_stellar or a broader TVL source. Adequate but not instructive.

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