ChainRay

Liquidation Alerts

monitor.liquidation

Read-onlyIdempotent

Monitor DeFi liquidation events on Aave V3. High liquidation counts indicate market stress and potential cascading risk.

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": "monitor.liquidation"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	EVM chain only. Supported chains: base, ethereum, arbitrum, optimism, polygon, bsc, avalanche, zksync, linea, scroll, blast, mantle, gnosis, polygon-zkevm, mode, sei, celo, manta, taiko, fantom, cronos, opbnb, zora, worldchain, metis, fraxtal, kava, zetachain, filecoin, core-dao, aurora, moonbeam, klaytn, bob, canto, monad, tempo, megaeth, arc, plasma, katana, robinhood, pharos, hyperevm.	base

Output Schema

Name	Required	Description
`chain`	Yes	Blockchain queried
`count`	No	Event count
`events`	No	Monitored events
`timestamp`	No	Unix timestamp ms

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 3, 2026
RemovedOct 2, 2026
First observedOct 2, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds interpretive context (high counts = stress/cascading risk) but no behavioral specifics such as polling cadence, time window of returned events, or rate limits, so it adds only modest value.

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?

Two tight sentences with the verb+resource front-loaded and no filler. The second sentence is slightly tangential interpretation rather than operational detail, keeping it just short of a 5.

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

Completeness3/5

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

An output schema exists so return values need not be explained, and the single param is fully documented. However, for a monitoring tool the description omits the observation window (real-time vs historical), event volume, and threshold semantics, which an agent needs to interpret results correctly.

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?

The single 'chain' parameter has 100% schema description coverage including the full enum and a documented default of 'base', so the schema does the heavy lifting. The description adds nothing about chain selection or default behavior, making baseline 3 appropriate.

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 and resource (monitor DeFi liquidation events) plus a protocol scope (Aave V3), which an agent can act on. It does not explicitly distinguish itself from siblings like monitor.flashloan or monitor.whale.alerts, but the liquidation/Aave focus is distinct enough to route correctly.

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

Usage Guidelines2/5

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

No when-to-use vs when-not-to-use guidance and no named alternatives among the many monitor.* siblings. The market-stress interpretation hints at intent but never states a condition for selecting this tool over defi.health or analyze.risk_dashboard.

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

All ChainRay 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?