Skip to main content
Glama
szhygulin

recon-crypto-mcp

by szhygulin
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

get_market_incident_status

Read-onlyIdempotent

Scan compound-v3 and aave-v3 markets for pause flags, frozen status, and utilization ≥95%; also monitor base-layer chains for stalling, skip rates, and concentration anomalies to flag incidents.

Instructions

Return an 'is anything on fire' snapshot across every registered market for a protocol + chain. For Compound V3, returns per-market pause flags, utilization, totalSupply, totalBorrow. For Aave V3, returns per-reserve isActive/isFrozen/isPaused, utilization, totalSupplied, totalBorrowed. Each entry has a flagged bit: Compound flags on any pause or utilization ≥ 95% (borrowers trapped); Aave flags on paused/frozen/inactive or utilization ≥ 95%. Top-level incident: true if any market/reserve is flagged. Use when you suspect a governance pause, a utilization cliff, or multi-market contagion from a shared-collateral exploit — collapses what would otherwise take one get_compound_market_info call per market.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
protocolYesWhat to scan. EVM lending: compound-v3 flags per-Comet pause + utilization, aave-v3 flags per-reserve isPaused/isFrozen/!isActive + utilization. Base-layer chains: bitcoin/litecoin compute tip_staleness + hash_cliff + empty_block_streak + miner_concentration; solana computes slot_progression + skip_rate + validator_concentration + cluster_halt + epoch_progression + priority_fee_anomaly; tron computes block_progression + missed_blocks_rate + sr_concentration + sr_rotation_anomaly + tronGrid_divergence + network_resource_exhaustion (and usdt_blacklist_event when `wallet` is supplied). solana-protocols scans for recent_program_upgrade + token_freeze_event + Pyth oracle_staleness against the user's exposure when `wallet` is supplied.
chainNoEVM chain (used by compound-v3 / aave-v3 only; ignored otherwise).ethereum
walletNoWallet address — used by `solana-protocols` (SPL exposure scope) and `tron` (TRC-20 USDT counterparty blacklist scope, issue #249). Solana base58 (43-44 chars) for `solana-protocols`; TRON base58 (T-prefix, 34 chars) for `tron`. Ignored on other protocols.

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations (readOnlyHint, idempotentHint, openWorldHint) indicate safe, read-only operation. Description adds concrete behavioral details: returns flagged bit, incident flag, utilization thresholds, and per-protocol logic, beyond what annotations provide.

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?

Well-structured and front-loaded with purpose, but somewhat dense with repeated protocol details. Could be slightly more concise without losing clarity.

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?

No output schema exists, but description fully explains return fields (flagged bit, incident flag, per-reserve flags, utilization, supply, borrow). Covers all protocols and edge cases adequately.

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

Parameters5/5

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

Schema coverage is 100% with descriptions for all parameters. Description adds value by explaining how each enum value affects return logic (e.g., bitcoin computes hash_cliff, empty_block_streak) and wallet usage for specific protocols.

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 states it returns an 'is anything on fire' snapshot across markets, with per-protocol details (Compound, Aave, base-layer chains). It distinguishes itself from sibling get_compound_market_info by collapsing multiple calls into one.

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?

Explicitly advises use when suspecting governance pause, utilization cliff, or multi-market contagion. Contrasts with get_compound_market_info for alternative when detailed per-market info is needed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/szhygulin/recon-crypto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server