Skip to main content
Glama
PagerDuty

pagerduty-mcp

Official
by PagerDuty

get_escalation_policy

Read-onlyIdempotent

Retrieve details of a specific escalation policy by its ID. Returns policy rules, targets, and configuration.

Instructions

Get a specific escalation policy.

Args:
    policy_id: The ID of the escalation policy to retrieve

Returns:
    Escalation policy details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
policy_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe ID of the escalation policy
nameYesThe name of the escalation policy
teamsNoThe teams associated with this escalation policy
summaryNoA short-form, server-generated string that provides succinct information about the escalation policy
html_urlNoThe URL at which this escalation policy is accessible in the PagerDuty UI
self_urlNoThe API URL at which this escalation policy is accessible
servicesNoThe services that are using this escalation policy
num_loopsNoThe number of times the escalation policy will repeat after reaching the end of its escalation
created_atNoThe date/time when this escalation policy was created
updated_atNoThe date/time when this escalation policy was last updated
descriptionNoThe description of the escalation policy
escalation_rulesYesThe ordered list of escalation rules for the policy
on_call_handoff_notificationsNoDetermines how on call handoff notifications will be sent for users on theescalation policyif_has_services
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no behavioral information beyond what the annotations provide, such as rate limits, authentication needs, or return value structure. Minimal value added.

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 concise: one sentence for the purpose, followed by a clear args/returns structure. Every sentence serves a purpose without unnecessary fluff. However, it could be slightly more structured by separating narrative from docstring.

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?

Given the tool's simplicity (single required parameter, output schema exists), the description covers the basics: get by ID and return details. It does not mention related tools for obtaining IDs or any side effects. With annotations covering safety, it is minimally adequate.

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?

With 0% schema description coverage, the description must compensate, but it only restates the parameter as 'The ID of the escalation policy to retrieve,' which adds little beyond the schema's title 'Policy Id.' No additional constraints or format details are provided.

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 clearly states 'Get a specific escalation policy,' specifying the verb 'Get' and the resource 'escalation policy.' This distinguishes it from sibling tools like list_escalation_policies, which performs a different operation. However, it lacks additional context about what an escalation policy is.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a policy ID from list_escalation_policies) or when not to use it. The only implied usage is that it requires a policy_id, but no explicit usage context is given.

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