Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

Search Incidents

search_incidents
Read-only

Search Rootly incidents by title or summary and control pagination to fetch all matching results or a specific page.

Instructions

Search incidents with flexible pagination control.

Use page_number=0 to fetch all matching results across multiple pages. Use page_number>0 to fetch a specific page.

max_results (also accepted as limit) caps how many incidents come back in either mode: across pages when page_number=0, and within the page otherwise. Left unset, a single page returns page_size incidents and page_number=0 stops at 5.

Argument caps: page_size <= 20, max_results <= 10. Values outside those bounds are clamped and reported, not rejected.

Input Schema

NameRequiredDescriptionDefault
queryNoSearch query to filter incidents by title/summary
page_sizeNoNumber of results per page (max: 20)
max_resultsNoMaximum incidents to return. Max: 10; defaults to 5 when fetching all pages, and to page_size when fetching a single page. For larger result sets, paginate with page_number > 0 or use collect_incidents.
page_numberNoPage number to retrieve (use 0 for all pages)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful behavioral details beyond annotations: out-of-bounds values are clamped and reported rather than rejected, max_results is also accepted as limit, and defaults differ between all-pages and single-page modes.

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 purpose and then organized around pagination modes and caps. It is somewhat repetitive with the schema, but every sentence provides operational guidance and there is no filler.

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

Completeness4/5

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

An output schema exists and annotations cover the safety profile, so the description does not need to explain return values. It thoroughly covers pagination and result caps, though it could be more complete by differentiating this tool from sibling incident-search and incident-list tools.

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 description coverage is 100%, so the schema already documents the parameters well. The description still adds value by clarifying the page_number=0 all-pages mode, the max_results cap across pages versus within a page, the limit alias, and clamping behavior.

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 states a specific verb and resource: 'Search incidents.' It is clear what the tool does, but it does not distinguish itself from siblings such as list_incidents, collect_incidents, or find_related_incidents.

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?

The description explains how to use page_number=0 versus page_number>0 and how max_results behaves in each mode. However, it gives no guidance on when to choose this tool over list_incidents or collect_incidents, so tool-selection guidance is only implied.

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