Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_chainflip

Paid. Chainflip 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/chainflip.

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

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 zero annotations the description carries the full burden and does well: it discloses cost ($0.01 USDC), accepted payment chains (Base or Solana), no auth requirement, and failure semantics ('Failed calls not charged'), plus live-data freshness. What is missing is rate limiting and any note on response shape or data latency, which keeps it below 5.

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 resource, then cost, then access terms, then the endpoint URL — no filler. The telegraphic sentence fragments are dense and readable, though a slightly tighter grouping of the payment/access facts would be cleaner.

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 endpoint with no output schema, the description covers what data comes back, what it costs, how to pay, and that failed calls are free — enough to invoke it confidently. Missing only response format details and rate/limit behavior, which would fully close the gap given the absent output schema.

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 no parameters, so the baseline is 4; there is nothing to document and the description does not invent or obscure any inputs. It correctly presents this as a parameterless fixed-resource purchase.

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 the exact resource (Chainflip TVL in DeFi) plus the payload contents (1d/7d/30d change) and the data source (DefiLlama), which cleanly separates it from the ~50 sibling buy_tvl_* tools. An agent can tell what it returns 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 Guidelines3/5

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

Use is implied by the resource name and the 'Paid' marker, and prerequisite context (no account, no API key) is stated, but there is no explicit guidance on when to prefer this over the other buy_tvl_* endpoints or which chain-level TVL queries it supersedes. Adequate but leaves selection to inference.

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