Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

Get Alert Route

get_alert_route
Read-only

Retrieve a specific alert route by ID to inspect routing configuration and, when needed, include nested destination and condition IDs for updates or deletions.

Instructions

Get a specific alert route by id. Note: This endpoint requires access to Advanced Alert Routing. If you're unsure whether you have access to this feature, please contact Rootly customer support.

Optional Parameters

  • show_nested_ids (query parameter): When set to true, the response will include IDs for all nested resources (destinations, condition_groups, conditions). This is useful when you need to reference these nested resources for updates or deletions via PATCH requests.

Example: GET /v1/alert_routes/{id}?show_nested_ids=true

Input Schema

NameRequiredDescriptionDefault
idYesRequired. ID of the alert route (fills `{id}` in /v1/alert_routes/{id}). Pass it as `id` -- this tool has no `alert_route_id` argument.
show_nested_idsNoInclude the IDs of nested destinations, condition groups and conditions, for referencing them in PATCH updates or deletions

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is a safe read-only operation. The description adds meaningful behavioral context by disclosing the Advanced Alert Routing access requirement and explaining how show_nested_ids enables later PATCH updates or deletions.

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 description is front-loaded with the core action and then uses a short optional-parameter section for supporting detail. It is slightly longer than strictly necessary, but the access note and parameter rationale both earn their place.

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 the output schema and full schema description coverage, the description provides the remaining context an agent needs: access eligibility and the purpose of the optional nested-ID behavior. Nothing essential for correct invocation is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining why show_nested_ids matters and providing a concrete request example, going beyond the schema's field-level description.

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 a specific alert route by id." This clearly distinguishes it from sibling operations such as list_alert_routes, create_alert_route, and update_alert_route.

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?

It clearly implies usage when a specific alert route id is known and adds an important access prerequisite for Advanced Alert Routing. It does not explicitly name alternatives like list_alert_routes for discovering ids, but the context is still clear.

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