Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

Get Ai Automation

get_ai_automation
Read-only

Retrieve a specific AI automation by ID to inspect its prompt, triggers, destination, allowed tools, skills, and run limits. Verify read-only how scheduled, event-driven, or on-demand automations run.

Instructions

Get one AI automation by id: its prompt, triggers, destination, allowed tools, attached skills and run limits. Read-only. An AI automation is a saved instruction (prompt) that a Rootly AI agent runs on a schedule, on a matching event (incident, alert, Slack message, webhook) or on demand. When it runs, the agent may only use the tools listed in the automation's allowed_tool_keys (all team-allowed tools when null), and it posts its answer to the configured destination (a Slack channel or the incident timeline), or nowhere when destination_kind is none.

Requires OAuth scope ai.automations:read.

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

Input Schema

NameRequiredDescriptionDefault
idYesRequired. ID of the automation (fills `{id}` in /v1/ai/automations/{id}). Pass it as `id` -- this tool has no `automation_id` argument.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: the required OAuth scope 'ai.automations:read' and domain semantics such as what null allowed_tool_keys means and what destination_kind none implies. It does not cover error or not-found behavior, but with annotations and an output schema present, this is solid.

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?

The first sentence is front-loaded and tells the agent exactly what the tool returns. The middle paragraph explaining what an AI automation is runs long, but it earns some of its space by clarifying how allowed_tool_keys and destination_kind affect interpretation of the returned object.

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?

For a single-parameter read tool with full schema coverage, annotations, and an output schema, the description supplies everything needed: purpose, auth scope, and enough domain context to interpret the returned fields. Nothing critical for correct invocation is missing.

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 description coverage is 100%, and the schema already explains the id parameter thoroughly, including the note that this tool has no automation_id argument. The description only says 'by id' and adds no syntax, format, or sourcing guidance beyond what the schema provides, so the baseline of 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 opens with a specific verb and resource: 'Get one AI automation by id,' then enumerates the returned fields (prompt, triggers, destination, allowed tools, skills, run limits). The singular 'one ... by id' framing distinguishes it from sibling list tools such as list_ai_automations without needing to name them.

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

Usage Guidelines3/5

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

Usage is only implied by 'by id' — the agent can infer this is for when an automation id is already known. The description never explicitly says when to use this versus list_ai_automations for discovery, nor does it state any exclusions or prerequisites beyond the OAuth scope.

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