Pagerlane MCP Connector

keep_list_incidents

Read-only

List incidents with filters for status, severity, assignees, sources, affected services, and CEL queries, plus pagination and sorting to find relevant active or predicted issues.

Instructions

List incidents. GET /incidents with limit, offset, sorting, cel, candidate, predicted, and the declared status, severity, assignees, sources, affected_services query params.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "keep_list_incidents"
  }
}

Input Schema

Name	Required	Description
`cel`	No	CEL filter.
`limit`	No	Page size. Keep default is 25.
`offset`	No
`status`	No
`sorting`	No	Keep IncidentSorting value.
`sources`	No
`severity`	No
`assignees`	No
`candidate`	No
`predicted`	No
`affected_services`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the HTTP verb/path, which is minor context; it says nothing about result ordering guarantees, default page size behavior, or how CEL interacts with the other filters.

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?

Two short sentences, front-loaded with the purpose and followed by the supporting detail; nothing is padded. However, the second sentence is a bare parameter dump that consumes space without earning it semantically.

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?

For an 11-parameter list tool with no output schema, the definition is thin: it does not describe the response shape, pagination/total-count behavior, or the semantics of the undocumented boolean flags. An agent would have to guess at how candidate/predicted alter results.

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 only 27%, so the description must compensate, and it does not. It merely re-lists parameter names already present in the schema; the two most opaque params, candidate and predicted booleans, are explained nowhere, and 'the declared status, severity...' adds no meaning beyond the names.

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 opens with a specific verb+resource ('List incidents') and pins it to the concrete endpoint GET /incidents, so an agent can tell it apart from keep_get_incident or keep_update_incident by operation type. It stops short of naming those siblings explicitly, but the resource is unambiguous.

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: 'List incidents' plus the endpoint suggests browser-style retrieval, and the enumerated filter params hint at filtering. There is no explicit when-to-use vs. keep_get_incident or keep_search_alerts, and no guidance on paging strategy despite limit/offset being present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server