Skip to main content
Glama

SouthPow crypto & market data

buy_tvl_arc

Paid. Arc 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/arc.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the disclosure burden and does well: it flags the tool as paid, states the exact price and payment chains, notes no account/API key is needed, and specifies that failed calls are not charged — critical for an agent deciding whether to spend. It stops short of describing response shape or rate limits.

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?

Roughly four short sentences with the payment status front-loaded in a single word ('Paid.'), then data content, then cost/access, then failure policy. Nothing is padded and the endpoint URL is compact supporting 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 fetch with no output schema, the description covers the essentials an agent needs: what the number is, what change windows are included, what it costs, how to pay, and that failures are free. Only the concrete return structure is left unstated, which is a minor gap given the simplicity.

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 input schema is empty, so there are no parameters whose meaning needs explaining. The description correctly adds nothing about arguments and instead spends its words on data content and payment behavior.

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 a specific resource and metric (Arc chain TVL in DeFi), the exact data content (live value plus 1d/7d/30d change), and the upstream source (DefiLlama). Against the large family of buy_tvl_<chain> siblings, the chain name in the first sentence makes selection unambiguous.

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 context is implied rather than stated: an agent infers it should call this for Arc chain TVL and the sibling buy_tvl_* tools for other chains. The description does clarify access requirements (no account, no API key) and payment rails, but gives no explicit when-to-use/when-not or pointer to an alternative tool.

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