Skip to main content
Glama
@atlasyield/mcp

@atlasyield/mcp

List open alerts

list_open_alerts
Read-onlyIdempotent

Retrieve open blowup-monitor alerts from the daily snapshot to review score-band exits, yield collapse, TVL flight, exploit flags, and delistings with before/after scores and pillar deltas.

Instructions

Open blowup-monitor alerts from the published daily snapshot: score-band exits, fast composite breaks, yield collapse, TVL flight, exploit flags, delistings. Each event carries score before/after and pillar deltas. Published once a day; the date field says when. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
chainIdNoRestrict to one chain id
minSeverityNoOnly alerts at or above this severity (1 = lowest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description correctly focuses on data-freshness behavior: alerts come from a snapshot published once per day, not live state, and each event carries score before/after plus pillar deltas. It stops short of pagination, retention across days, or whether an alert can disappear between snapshots.

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?

Three tight sentences with the resource and its categories front-loaded, followed by return content and then cadence. The long category list is dense but each item earns its place by telling the agent what kinds of events to expect.

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?

With no output schema, the description carries the return-value burden and does so reasonably by naming the per-event fields (score before/after, pillar deltas). The daily-snapshot cadence is the key operational caveat. Remaining gaps are minor: no pagination/limit behavior and no indication of typical volume.

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?

Schema description coverage is 100% for both chainId and minSeverity, so the schema already carries the semantics and the baseline of 3 applies. The description adds no filtering guidance and its mention of 'the date field says when' refers to returned data rather than either declared parameter, so it does not enrich parameter meaning.

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?

Specific verb (list) plus resource (open blowup-monitor alerts) and an enumeration of the alert categories it returns (score-band exits, composite breaks, yield collapse, TVL flight, exploit flags, delistings). This makes it unmistakable against siblings like get_vault_score or check_route_survival, which are per-vault tools.

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 is implied by the content, but there is no explicit when-to-use statement, no when-not-to-use, and no mention of any sibling tool as an alternative. The daily-cadence note hints at freshness expectations but does not tell the agent when this tool is the right pick.

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