Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_tezos

Paid. Tezos 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/tezos.

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

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 provided, the description carries the full burden and does well: it discloses the cost, accepted payment networks, absence of authentication, and the notable billing behavior that failed calls are free. Remaining gaps are rate limits, response format and latency, which are not mentioned.

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-loads the single most consequential fact ('Paid.') and then packs resource, data source, price, payment rails, billing policy and endpoint into a few dense fragments. No filler sentences; every clause carries actionable information.

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 paid data endpoint with no output schema, the description covers cost, payment, auth model, data provenance and the fields returned (TVL plus change windows). It could be slightly more complete by sketching the response shape or units, but an agent has everything needed to decide and call.

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 applies. The description correctly implies the call is fully determined by the endpoint (chain is baked into the path).

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 a specific resource (Tezos DeFi total value locked), its source (DefiLlama), and the exact payload contents (live value plus 1d/7d/30d change). The chain name in the description makes it trivially distinguishable from the large family of sibling buy_tvl_* tools covering other chains.

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 concrete operational prerequisites for use: paid ($0.01 USDC), payable on Base or Solana, no account or API key required, and failed calls are not charged. It stops short of explicitly routing between alternatives (e.g. when to prefer a different chain's TVL tool or a broader DeFi endpoint), but the paid-fetch context is clear.

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