pagerduty-mcp-community

get_escalation_policy

Read-onlyIdempotent

Retrieve details of a specific escalation policy by providing its policy ID. Use this to view escalation rules and targets for incident routing.

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

Name	Required	Description	Default
`policy_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	The ID of the escalation policy
`summary`	Yes	A short-form, server-generated string that provides succinct information about the escalation policy
`name`	Yes	The name of the escalation policy
`description`	No	The description of the escalation policy
`escalation_rules`	Yes	The ordered list of escalation rules for the policy
`num_loops`	No	The number of times the escalation policy will repeat after reaching the end of its escalation
`on_call_handoff_notifications`	No	Determines how on call handoff notifications will be sent for users on theescalation policy	if_has_services
`self_url`	No	The API URL at which this escalation policy is accessible
`html_url`	No	The URL at which this escalation policy is accessible in the PagerDuty UI
`services`	No	The services that are using this escalation policy
`teams`	No	The teams associated with this escalation policy
`created_at`	No	The date/time when this escalation policy was created
`updated_at`	No	The date/time when this escalation policy was last updated

Tool Definition Quality

B3.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the tool is safe and non-destructive. The description adds no extra behavioral details beyond stating it retrieves details. It does not mention permissions, caching, or any side effects.

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 very concise: one line plus docstring structure. The main purpose is front-loaded. It is appropriately sized for a simple get operation, though it could include more structure without adding length.

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?

The tool is simple (one parameter, no nested objects) and has an output schema (implied). The description provides minimal but adequate context for a straightforward retrieval. However, it lacks details on the output structure or any error conditions, which would be helpful.

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?

The schema has one parameter 'policy_id' with type string and no description. The description repeats 'The ID of the escalation policy to retrieve,' adding no semantic value beyond what the schema title 'Policy Id' provides. Schema description coverage is 0%, and the description does not compensate.

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 explicitly states 'Get a specific escalation policy.' The verb 'Get' and the resource 'escalation policy' are clear. The naming and description distinguish it from sibling tool 'list_escalation_policies,' which retrieves multiple policies.

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 implies usage when a specific policy_id is known, but it does not explicitly state when to use this tool versus alternatives like 'list_escalation_policies.' No exclusion criteria or context are provided.

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

Install Server

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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