Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

get_chain_tvl

Read-onlyIdempotent

Total Value Locked for a whole blockchain such as Ethereum, Base or Solana. Returns USD TVL and the top protocols on that chain. Use it when the user asks about a chain's overall DeFi footprint.

[Access: pay 0.01 USDC via x402 (PAYMENT-SIGNATURE header) OR authenticate with an API key. An x402-capable client will auto-pay; API-key clients pay nothing per call.]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "<chain>"
    },
    "name": "get_chain_tvl"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesChain name or slug, e.g. ethereum or base.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds genuine value by disclosing the access model: 0.01 USDC via x402 PAYMENT-SIGNATURE header or an API key, with x402 clients auto-paying. Return contents are also sketched.

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 the resource and return value, then usage guidance, with the payment/auth caveat set off in brackets. Every sentence carries information; slight redundancy between the examples and the schema is the only waste.

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?

No output schema exists, so the description usefully states what comes back (USD TVL and top protocols). Combined with the access/payment disclosure and full param coverage, an agent has everything needed to call it correctly, though the payment flow could be spelled out further.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter with 100% schema description coverage, so the schema already documents 'chain' fully. The description's chain examples (Ethereum, Base, Solana) largely duplicate the schema's own 'e.g. ethereum or base', adding no new syntax or slug rules.

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 verb+resource ('Total Value Locked for a whole blockchain') and names the return shape (USD TVL plus top protocols). The 'whole blockchain' framing implicitly contrasts with the sibling get_protocol_tvl, though it never names that alternative directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

'Use it when the user asks about a chain's overall DeFi footprint' gives a clear triggering context. It stops short of an explicit exclusion (e.g. 'for a single protocol, use get_protocol_tvl instead'), so the agent must infer the boundary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MangroveAI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources