Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

Acknowledge Alert

acknowledge_alert
Destructive

Acknowledge a specific Rootly alert by ID to mark it as being handled and prevent duplicate response efforts.

Instructions

Acknowledges a specific alert by id

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": {
      "id": "<id>"
    },
    "name": "acknowledge_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. ID of the alert (fills `{id}` in /v1/alerts/{id}/acknowledge). Pass it as `id` -- this tool has no `alert_id` argument.
dataNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the risk profile is known. The description adds nothing beyond that: it doesn't say what acknowledging changes (escalation, notification, on-call state), whether it can be undone, or anything about the actor-attribution option in the payload.

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

Conciseness3/5

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

One short, front-loaded sentence with no filler, but its brevity stems from under-specification rather than tight editing. There is no room wasted, yet little is conveyed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, non-idempotent mutation with a nested payload; the description never covers effects, reversibility, or actor attribution, relying entirely on annotations and schema. An output schema exists, so return values need not be described, but the behavioral gaps remain.

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

Parameters2/5

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

Schema coverage is 50% and the description only repeats 'by id', which the schema's id field already documents in detail. It says nothing about the nested data/attributes wrapper or when the actor block is honored, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Acknowledges a specific alert by id'. An agent can tell this changes an alert's acknowledgement state, though it doesn't distinguish itself from siblings like resolve_alert or update_alert.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of when an agent should prefer resolve_alert or update_alert instead. The only usage hint is that an id is required, which the schema already enforces.

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