Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_ink

Paid. Ink 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/ink.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 on the operational side: it discloses that the call is paid, the exact price and accepted payment chains, that no account or API key is needed, and that failed calls are not charged. It omits anything about rate limits, latency, or caching, and says nothing about the response shape beyond the metrics included.

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?

Dense and front-loaded: the 'Paid' marker leads, then what the data is, then cost and access terms. The trailing endpoint URL is arguably scaffolding rather than decision-relevant information, which keeps it from a 5, but no sentence is filler.

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 data-purchase endpoint with no output schema, the description supplies the chain, the metrics, the freshness ('live'), the source, and the full payment model. The remaining gap is return-value structure, which would be useful given no output schema exists.

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 beyond what the input schema shows. Baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: Ink chain total value locked in DeFi, live, with 1d/7d/30d change, sourced from DefiLlama. The chain name in the tool name and description cleanly separates it from the other buy_tvl_* siblings, though the description never explicitly routes to an alternative.

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 ('Ink TVL') but there is no explicit when-to-use / when-not-to-use guidance or comparison to siblings such as buy_yields_chain_ink. The payment terms ($0.002, no account, failed calls not charged) do give an agent the cost context needed to decide whether to call.

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