Skip to main content
Glama
PagerDuty

pagerduty-mcp

Official
by PagerDuty

list_event_orchestrations

Read-onlyIdempotent

Retrieve a list of event orchestrations with optional pagination and sorting by name, routes, or creation date.

Instructions

List event orchestrations with optional filtering.

Args:
    limit: The number of results per page. Default 100.
    offset: Offset to start pagination search results.
    sort_by: Field and direction to sort by. Default 'name:asc'. Options:
        'name:asc', 'name:desc', 'routes:asc', 'routes:desc',
        'created_at:asc', 'created_at:desc'.

Returns:
    List of event orchestrations matching the query parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
sort_byNoname:asc

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
responseYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is clear. The description adds that it returns a list, which is expected. No additional behavioral traits disclosed, but with annotations present, this is adequate.

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?

Well-structured with Args and Returns sections. Short, front-loaded purpose, every sentence adds value. No unnecessary verbiage.

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

Completeness4/5

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

Given 3 optional parameters, an output schema exists, and standard list behavior, the description is complete. It explains filtering and sorting. No gaps for selecting and invoking the tool correctly.

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?

Schema description coverage is 0%, so the description carries the full burden. It explains each parameter (limit, offset, sort_by) with defaults and enum options, adding significant meaning beyond the raw schema.

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?

Clearly states 'List event orchestrations with optional filtering' – verb and resource are specific. However, it does not explicitly distinguish from sibling tools like get_event_orchestration, but the name and plural form imply listing multiple, so it's clear.

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?

Implied usage: used to list event orchestrations with filtering. No explicit when-to-use, when-not-to-use, or alternatives mentioned. The description could benefit from stating when to use this vs. get_event_orchestration for a single item.

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