Skip to main content
Glama
Sign In
RedAlert MCP Server

RedAlert MCP Server

by ozba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

poll_alerts

Retrieve buffered real-time alerts received since the last poll. Requires an active subscription from subscribe_alerts.

Instructions

Retrieve buffered real-time alerts that arrived since the last poll. Must call subscribe_alerts first.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of alerts to return (default 50, max 200)
acknowledgeNoIf true (default), clear returned alerts from buffer. If false, peek without consuming.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It explains the polling nature, buffer consumption via acknowledge parameter, and the requirement of prior subscription. It could be more detailed about rate limits or return format, but adds sufficient behavioral context.

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

Conciseness5/5

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

Two sentences front-loaded with the core purpose and a crucial prerequisite. Every sentence adds value, no wasted words.

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?

The description explains the tool's polling mechanism and buffer behavior well. Without an output schema, it could hint at the return format (e.g., list of alerts), but the description is sufficient for a simple poll tool given the context of sibling tools.

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 coverage is 100% with both parameters described in the schema. The description does not add additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 the verb 'Retrieve' and the resource 'buffered real-time alerts that arrived since the last poll'. It differentiates from sibling tools like get_active_alerts by specifying polling behavior.

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?

The description explicitly states 'Must call subscribe_alerts first', providing a clear prerequisite and guiding the agent to not use this tool without prior subscription.

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

Deploy Server

Other Tools