Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

Resolve Alert

resolve_alert
Destructive

Resolves a specific Rootly alert by ID and optionally records the actor, a resolution message, and whether related incidents should be resolved.

Instructions

Resolves 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": "resolve_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. ID of the alert (fills `{id}` in /v1/alerts/{id}/resolve). 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.7/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 safety profile is covered structurally. The description adds nothing beyond that — it does not say the action is irreversible, that it may cascade to associated incidents, or that actor attribution depends on org settings and key type, all of which live only in the schema.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, but the efficiency comes at the cost of under-specification rather than deliberate brevity.

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 mutation with a nested object payload and optional cascade behavior, yet the description covers only the identifier. An output schema exists so return values need not be explained, but the mutating semantics, attribution constraints, and incident-resolution side effect are all absent from the description.

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?

The phrase "by id" merely restates the required `id` parameter, which the schema already documents in detail, including the warning about there being no `alert_id` argument. With 50% schema coverage, the description needed to explain the `data.attributes` payload (resolution_message, actor, resolve_related_incidents) and does not.

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?

The description names a specific verb and resource ("Resolves a specific alert by id"), so an agent knows exactly what operation is performed. It offers no differentiation from siblings like update_alert or acknowledge_alert, which is the only thing separating it from a 5.

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?

There is no guidance on when to pick this over acknowledge_alert/update_alert, no prerequisites, and no mention of what state the alert must be in. The only usable signal is the implicit notion that 'resolve' is a distinct terminal action, which an agent must infer.

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