Skip to main content
Glama
Sign In
RedAlert MCP Server

RedAlert MCP Server

by ozba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

unsubscribe_alerts

Stop receiving real-time rocket alerts by disconnecting from the RedAlert server. Clears the alert buffer to reset your alert state.

Instructions

Disconnect from RedAlert Socket.IO server and stop receiving real-time alerts. Clears the alert buffer.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Discloses key behaviors: disconnecting from server, stopping real-time alerts, and clearing the alert buffer. With no annotations, it adequately describes effects, though error cases or side effects are not mentioned.

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?

Extremely concise two-sentence description, front-loaded with the primary action. Every word adds value with no redundancy.

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 zero parameters, no output schema, and a clear sibling context (subscribe_alerts), the description is fully adequate. It covers the purpose, effect, and complements the sibling tool well.

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?

No parameters present, so schema coverage is 100%. The description correctly adds no parameter info, meeting the baseline for zero-parameter tools.

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?

Clearly states the action (disconnect from RedAlert Socket.IO server) and the result (stop receiving alerts, clear buffer). Distinguishes itself from sibling subscribe_alerts which does the opposite.

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

Usage Guidelines4/5

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

Implies usage when user wants to stop alerts, and the sibling subscribe_alerts suggests the opposite action. No explicit when-not-to-use, but context is sufficient given the tool's simplicity.

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