Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_xpr-network

Paid. XPR Network 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/xpr-network.

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_xpr-network"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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: it discloses payment requirement, exact price, accepted chains for payment, absence of auth, and the failed-call refund behavior. Not covered are freshness guarantees (what 'live' means), rate limits, or the shape of the returned fields, which keeps it from a 5.

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 most decision-relevant fact ('Paid.') and then packs resource, cadence of change data, source, price, payment rails, and endpoint into a tight sequence with no filler sentences. Everything present either affects the decision to call or the mechanics of paying.

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 supplies what an agent needs: what data comes back, its source, cost, payment methods, and failure charging policy. The remaining gap is the absence of any hint about the response structure or units, which the missing output schema would otherwise have covered.

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 to disambiguate and the baseline of 4 applies. The description correctly implies no configuration is needed by stating no account or API key is required.

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 the resource precisely: XPR Network total value locked in DeFi, live, with 1d/7d/30d changes, sourced from DefiLlama. That distinguishes it from the many sibling buy_tvl_* tools, which cover other chains. The only weakness is that the action verb is implicit – it reads as a data listing rather than saying 'returns/fetches' – though the 'buy_' name prefix supplies the purchase framing.

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?

Conveys the cost model ($0.005 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged, which is useful context for deciding whether to call. It gives no explicit when-to-use or when-not-to-use guidance, such as pointing to buy_tvl_* siblings for other chains or to get_schema for endpoint details.

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