Skip to main content
Glama
Orchestra MCP Server

Orchestra MCP Server

Official
by orchestra-hq

List incidents

list_incidents
Read-only

Retrieves incidents for a workspace, most severe first, with merged children nested under parents. Filter top-level incidents by name, status, severity, or creation date and paginate results.

Instructions

List incidents for the workspace the credential resolves to, most severe first, with merged children nested under their parent.

Filters apply to top-level incidents only - a child is always returned alongside its parent, so a filtered list still shows the full incident rather than part of one. Use name to filter incidents by a case-insensitive substring match on the incident name. Use sort_column and sort_direction to sort top-level incidents by a single column instead; merged children keep the default order.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_incidents"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFilter by a case-insensitive substring match on the incident name.
pageNoPage number. Must be greater than or equal to 1.
statusNoFilter by status. Comma-separated values are supported.
severityNoFilter by severity. Comma-separated values are supported.
page_sizeNoNumber of items per page. Defaults to 10; maximum 100.
sort_columnNoColumn used to sort incidents. Defaults to open, most severe first.
created_beforeNoOnly incidents created before this time, as an ISO 8601 timestamp with a timezone.
sort_directionNoSort direction. Ignored unless `sort_column` is set.desc
include_archivedNoInclude archived incidents. Defaults to false.
X-Orchestra-Account-IdNoAct on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2026.10.29-0
    • addedInput schema / properties / created_before
      Added value: +{
      +  "anyOf": [
      +    {
      +      "format": "date-time",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Only incidents created before this time, as an ISO 8601 timestamp with a timezone."
      +}
  2. Changed2 schema fields changedv2026.10.12-0
    • addedInput schema / properties / sort_column
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "severity",
      +        "name",
      +        "created_at",
      +        "updated_at"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Column used to sort incidents. Defaults to open, most severe first."
      +}
    • addedInput schema / properties / sort_direction
      Added value: +{
      +  "default": "desc",
      +  "description": "Sort direction. Ignored unless `sort_column` is set.",
      +  "enum": [
      +    "asc",
      +    "desc"
      +  ],
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only safety, and the description adds genuinely non-obvious behavior: children are always returned with their parent so filters never produce partial incidents, and merged children keep default order when a custom sort is applied. It doesn't discuss permissions or result-count/pagination interaction with nested children, but the added behavioral context is substantive.

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?

Three tight sentences: what it lists and default order first, then the filter/child-nesting caveat, then per-parameter guidance. Every sentence carries information not present in the schema and nothing is repeated.

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?

With 10 parameters, an output schema, and full schema descriptions, the description covers the hardest part (merging + filtering interaction). It leaves one real gap: how `page`/`page_size` interact with nested merged children (whether children count toward page size) is unstated.

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 coverage is 100%, so the baseline is 3; the description earns above that by explaining the semantic trap that filters only apply to top-level incidents and that `sort_column` affects top-level ordering while children stay in default order. It doesn't elaborate on status/severity comma-separated filtering or include_archived, but the schema already documents those.

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?

States a specific verb+resource with scope ('incidents for the workspace the credential resolves to'), default ordering, and the merged-child nesting behavior. It's clear what the tool returns, though it never names or contrasts siblings like get_incident or list_incident_events, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operating context: filters apply to top-level incidents only, use `name` for substring filtering, and use `sort_column`/`sort_direction` instead when sorting is needed. It doesn't tell the agent when to prefer this over get_incident or list_incident_events, so there is no explicit alternative routing.

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

Deploy Server

Other Tools