Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_solana

Paid. Solana 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/solana.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 cost, accepted payment chains, absence of auth, and a billing-failure policy ('Failed calls not charged'), which is the most consequential behavior for a paid tool. It omits refresh cadence, rate limits, and the shape/units of the returned payload.

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-loaded with 'Paid.' then the resource and metric, followed by cost, auth, billing, and endpoint in a compact run of short sentences. Every clause adds information; nothing is redundant with the name or schema.

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, annotation-free tool with no output schema, the description does explain what data comes back (TVL plus 1d/7d/30d changes from DefiLlama), which is the essential completeness requirement. It stops short of describing response structure, currency units, or freshness guarantees.

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 usefully confirms the subject is fixed (Solana DeFi TVL with 1d/7d/30d changes) rather than leaving the caller to guess what the empty argument list implies.

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?

The description names a specific metric, chain and scope: 'Solana total value locked (TVL) in DeFi, live, with 1d/7d/30d change (DefiLlama data)'. Combined with the tool name, an agent can distinguish it from the many other buy_tvl_* chain siblings without opening anything else.

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?

It states the precondition that governs selection — this is a paid call at $0.01 USDC on Base or Solana, no account or API key, failed calls not charged — which is the key gating information for a paid data tool. It does not say when to prefer a different sibling (e.g. buy_yields_chain_solana or buy_cp_solana-ecosystem) or any when-not-to-use case.

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