Skip to main content
Glama
PagerDuty

pagerduty-mcp

Official
by PagerDuty

get_schedule_v3_rotation_event

Read-onlyIdempotent

Fetch details of a single event in a PagerDuty v3 schedule rotation using schedule, rotation, and event IDs.

Instructions

Get a specific event within a v3 schedule rotation.

Args:
    schedule_id: The ID of the v3 schedule
    rotation_id: The ID of the rotation
    event_id: The ID of the event

Returns:
    The rotation event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYes
rotation_idYes
schedule_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe ID of the rotation event
nameNoDisplay name for this event
selfNoAPI URL for this event
typeNoResource type identifier
end_timeNoZonedDateTime: {date_time, time_zone}
html_urlNoPagerDuty UI URL for this event
recurrenceNoRFC 5545 recurrence rules (e.g. ['RRULE:FREQ=WEEKLY'])
start_timeNoZonedDateTime: {date_time, time_zone}
effective_sinceNoISO 8601 datetime when this event starts producing shifts
effective_untilNoISO 8601 datetime when this event stops producing shifts. Null means indefinite.
assignment_strategyNoHow users are assigned on-call
Behavior2/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds no additional behavioral insight (e.g., no mention of side effects, permissions, or response details beyond using the parameter names).

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 succinct and front-loaded with the core purpose. However, it could include a brief sentence about when to use it without being verbose.

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?

While an output schema exists and the tool is simple, the description fails to link to necessary IDs (e.g., from list endpoints) or explain the hierarchical relationship among schedule, rotation, and event, reducing completeness for new users.

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 description coverage is 0%, but the description merely repeats parameter names with generic phrases like 'The ID of the v3 schedule' without adding formats, origins, or examples. This provides minimal semantic help over the 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?

The description clearly states 'Get a specific event within a v3 schedule rotation,' specifying the verb (get), resource (event), and context (v3 schedule rotation). It effectively distinguishes from sibling tools like list_schedule_v3_rotation_events and other get_ tools.

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., listing events or getting a rotation). The description does not provide any when-to-use, when-not-to-use, or prerequisite instructions.

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