Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_pulsechain

Paid. PulseChain total value locked (TVL) in DeFi, live, with 1d/7d/30d change (DefiLlama data). $0.002 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/defillama/tvl/pulsechain.

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

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 usefully discloses the exact price and currency, supported payment networks, lack of account or API-key requirements, and that failed calls are not charged. It also establishes live DefiLlama sourcing, though it leaves payment execution and precise response behavior unspecified.

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?

The description is compact and front-loaded, beginning with the paid nature and immediately defining the data provided. Pricing, authentication, failure billing, and URL details each add practical information without unnecessary wording.

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 simple zero-parameter data lookup, this supplies nearly everything needed for selection and invocation, including scope, source, endpoint, and commercial terms. Because there is no output schema, exact response structure, TVL denomination, and change-field formatting would make it more complete.

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 has no parameters, so there is no parameter documentation burden. The description confirms the fixed PulseChain scope and provides the specific endpoint URL.

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 clearly identifies a live lookup of PulseChain DeFi total value locked, including 1d/7d/30d changes and DefiLlama as the source. The chain and TVL scope distinguish it from other buy_tvl_* chains and from the buy_yields_* tools.

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?

An agent can readily infer that this is the appropriate choice for current PulseChain DeFi TVL and short-term percentage changes. It does not explicitly state when not to use it or name alternatives for other chains, historical analysis, or yield data.

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