Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_arbitrum

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

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

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 a decent job: it discloses that calls are paid, the exact price and accepted payment chains, that no auth is needed, that failed calls are not charged, and that data is live. It omits response format/pagination details, but the key behavioral risks (cost, auth, failure billing) are covered.

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?

Telegraphic but efficient: cost flag first, then what the data is, then payment/auth/failure terms, then the endpoint URL. Every sentence carries information, though the URL and payment details could arguably be pushed to structured metadata.

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 what is returned (TVL plus 1d/7d/30d change), freshness, source, price, and payment rails. Only minor gaps remain, such as the concrete response shape or units of the TVL figure.

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; baseline 4 applies. The schema is an empty object and the description correctly implies no inputs are needed.

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 metric (Arbitrum DeFi TVL) plus the returned fields (live value with 1d/7d/30d change) and the data source (DefiLlama). The chain qualifier in the name and description implicitly separates it from the many buy_tvl_* siblings, though it never explicitly says 'not 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 Guidelines3/5

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

Gives prerequisites and cost context well ('Paid', '$0.005 USDC on Base or Solana', 'No account, no API key'), which helps an agent decide whether it can call it. However, there is no explicit when-to-use/when-not guidance and no routing to adjacent siblings such as buy_tvl_ethereum or buy_yields_chain_arbitrum.

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