SiteCheck Crypto & Finance

Mantle Network L2 telemetry from the public Mantle RPC

crypto_mantle_da_eigenlayer

Read-only

Mantle Network L2 telemetry from the public Mantle RPC: latest block, safe block (its batch is posted to Ethereum/EigenDA) and finalized block with numbers, times and transaction counts, the head-to-safe and head-to-finalized lags in blocks and seconds, gas price (gwei), base fee, gas used % of limit and average block time over the last 20 blocks. Treasury AUM and per-blob EigenDA statistics are not in the RPC and are not reported. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "crypto_mantle_da_eigenlayer"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`head`	No
`safe`	No
`chain`	No
`source`	No
`chainId`	No
`checkedAt`	No
`finalized`	No
`headToSafe`	No
`gasPriceGwei`	No
`avgBlockTimeSec`	No
`headToFinalized`	No
`gasUsedPctOfLimit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the read-only nature provided by annotations, the description details crucial behavioral constraints including pricing ($0.002/call) and non-availability of specific metrics like Treasury AUM. This operational context is invaluable to the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While every piece of information is valuable and accurate, the description is extremely dense and long. It prioritizes comprehensive technical detail over brevity, making it less concise than ideal but still highly effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of L2 telemetry, the description is extremely complete. It defines the scope of data provided and, crucially, explicitly enumerates the known limitations of the RPC source, ensuring the agent has a full picture of the tool's capabilities.

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?

Although the input schema is empty, the description adds substantial semantic value by exhaustively listing all the output fields (e.g., 'head-to-safe and head-to-finalized lags'), allowing the agent to confirm it has the necessary information before invocation.

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?

The description clearly and specifically defines the tool's function as retrieving Mantle Network L2 telemetry, distinguishing it from general RPC calls. It lists precise data points like block lags, gas fees, and block time metrics.

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

Usage Guidelines5/5

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

It provides clear usage boundaries by listing exactly what metrics it reports, and equally important, stating explicitly what critical data (like AUM or per-blob stats) is unavailable. This guides the agent on when to and when not to use the tool.

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

All SiteCheck Crypto & Finance tools Inspect

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

Need Help?