Skip to main content
Glama
PagerDuty

pagerduty-mcp

Official
by PagerDuty

get_incident

Read-onlyIdempotent

Retrieve a specific incident by its ID or number to access full incident details, including optional additional information such as users, services, and assignments.

Instructions

Get a specific incident.

Args:
    incident_id: The ID or number of the incident to retrieve.
    query_model: Optional query parameters for additional information to include

Returns:
    Incident details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
incident_idYes
query_modelNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe ID of the incident
titleYesA succinct description of the nature, symptoms, cause, or effect of the incident
statusYesThe current status of the incident
serviceYesThe service the incident is on
summaryNoA short summary of the incident
priorityNoThe priority of the incident (e.g. P1, P2)
created_atYesThe time the incident was first triggered
updated_atYesThe time the incident was last modified
assignmentsNoThe users assigned to the incident
resolved_atNoThe time the incident became resolved or null if the incident is not resolved
incident_numberYesThe number of the incident. This is unique across your account
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds no significant behavioral context beyond 'Get', which is consistent. No contradictions.

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?

Short, structured with Args/Returns. No fluff, but could be slightly more concise with a single line.

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?

Adequate for a simple get tool with an output schema. Missing explanation of query_model options and when to use include. Satisfies minimum requirements.

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?

Incident_id is described clearly but query_model only says 'Optional query parameters'. The input schema already contains detailed descriptions for the nested include field. Description adds minimal value over schema.

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?

Description explicitly states 'Get a specific incident', clearly identifying the action and resource. This distinguishes it from siblings like list_incidents which retrieve multiple incidents.

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?

No guidance on when to use this tool versus alternatives (e.g., list_incidents for multiple, or other get_* tools). Usage must be inferred from context.

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/PagerDuty/pagerduty-mcp-server'

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