Skip to main content
Glama
carlyou

pagerduty-mcp-community

by carlyou

list_incidents

Read-onlyIdempotent

Filter and list PagerDuty incidents by status, dates, teams, or urgency to find precisely the incidents you need.

Instructions

List incidents with optional filtering.

Args:
    query_model: Optional filtering parameters

Returns:
    List of Incident objects matching the query parameters

Examples:
    Basic usage filtering by status:

    >>> from pagerduty_mcp.models import IncidentQuery
    >>> result = list_incidents(IncidentQuery(status=["triggered"]))
    >>> isinstance(result.response, list)
    True

    Multiple statuses with a limit:

    >>> result = list_incidents(IncidentQuery(status=["triggered", "acknowledged"], limit=10))

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
query_modelYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
responseYes
Behavior3/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that it performs optional filtering and returns a list, which is consistent but not rich. No additional behavioral details (e.g., pagination, rate limits) are disclosed beyond the schema's limit parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a header, Args, Returns, and a code example. It is concise and front-loads the core purpose. Every element serves a clear purpose without unnecessary verbosity.

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

Completeness3/5

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

While the description covers basic usage and includes examples, it omits explanations of pagination, sorting (though present in schema), and result format details. Given the tool's complexity (many filter parameters) and the existence of an output schema (not shown), the description is adequate but incomplete for an agent needing full context.

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?

The description provides the Args line 'query_model: Optional filtering parameters', adding minimal top-level parameter meaning since the schema lacks a description for query_model. The examples significantly enhance semantics by showing usage with IncidentQuery fields, compensating for the 0% schema description coverage of the top-level parameter.

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 clearly states 'List incidents with optional filtering', specifying the verb and resource. The name 'list_incidents' and sibling tools like 'get_incident' naturally differentiate, and the description reinforces the listing action.

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?

The description gives no guidance on when to use this tool versus alternatives like 'get_incident' for single incidents or other list tools. It does not mention exclusions or context, leaving the agent without clear decision-making criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/carlyou/pagerduty-mcp-community'

If you have feedback or need assistance with the MCP directory API, please join our Discord server