Skip to main content
Glama
Sign In
@argosvix/mcp-server

@argosvix/mcp-server

by argosvix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

acknowledge_alert

Acknowledge a specific alert event to indicate it has been handled while allowing future occurrences of the same rule.

Instructions

Mark an individual alert firing (event) as handled / acknowledged. Unlike silence_alert (which temporarily mutes the whole alert rule), ack is a per-event receipt — future firings of the same rule are still delivered as usual. Pass the id obtained from list_alert_events as eventId. Re-acking an already acknowledged event does not overwrite the existing ack info (the first acknowledgedAt / acknowledgedBy) and returns 200 (idempotent; distinguishable via the alreadyAcknowledged flag).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "eventId": "<eventId>"
    },
    "name": "acknowledge_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesEvent id to acknowledge (list_alert_events.events[].id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.30.0-alpha.14

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: per-event action, idempotent (does not overwrite ack info), return 200 with flag. No hidden traits.

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?

Three sentences, front-loaded with main action, then contrast, then details. Every sentence earns its place with no filler.

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 no output schema, description explains return behavior (200, flag) and idempotence. Sufficient for a simple acknowledge operation. Sibling tools cover related alert actions.

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 already describes eventId with origin note; description adds 'Pass the id obtained from list_alert_events as eventId', reinforcing correct usage. High schema coverage (100%) plus extra context.

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 it marks an alert event as acknowledged, and explicitly distinguishes from sibling silence_alert by explaining per-event vs rule-level 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?

Provides explicit guidance on when to use this tool (per-event ack) versus silence_alert (rule-level mute), and explains idempotent behavior with the alreadyAcknowledged flag.

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