Orchestra MCP Server

Official

by orchestra-hq

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Update a monitor

update_monitor

Replace a monitor's definition entirely. Omitted fields reset to defaults; order is preserved.

Instructions

Replace a monitor's definition with the one in the body. A field left out takes its default rather than keeping its stored value, except order, which keeps the monitor's place.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes
`match`	Yes	Which events a monitor claims: AND across dimensions, OR within a list. At least one dimension has to be given. A monitor matching every dimension by saying nothing would claim every event on the account, which is never what an author means.
`order`	No
`action`	No	What happens to the events this monitor claimed. ``mute`` claims them and sends no alert - the known-broken-thing case. They are still recorded, on incidents the monitor owns, so a mute is silent without being invisible.
`enabled`	No
`groupBy`	Yes
`trigger`	No
`monitor_id`	Yes	Monitor ID.
`description`	No
`X-Orchestra-Account-Id`	No	Act 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

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.1.2Oct 2, 2026

addedInput schema / properties / groupBy / items / anyOf

Added value: +[
+  {
+    "description": "What makes two events this monitor claimed one incident.\n\nEvery value but ``MONITOR`` resolves to a typed column that already exists on\n``incident_events``. ``MONITOR`` means \"everything this monitor claims is one\nincident\", which is served by ``monitor_id`` on the incident instead.",
+    "enum": [
+      "asset",
+      "task",
+      "pipeline",
+      "connection",
+      "monitor"
+    ],
+    "type": "string"
+  },
+  {
+    "pattern": "^\\$",
+    "type": "string"
+  }
+]

removedInput schema / properties / groupBy / items / description

Removed value: -"What makes two events this monitor claimed one incident.\n\nEvery value but ``MONITOR`` resolves to a typed column that already exists on\n``incident_events``. ``MONITOR`` means \"everything this monitor claims is one\nincident\", which is served by ``monitor_id`` on the incident instead."

removedInput schema / properties / groupBy / items / enum

Removed value: -[
-  "asset",
-  "task",
-  "pipeline",
-  "connection",
-  "monitor"
-]

removedInput schema / properties / groupBy / items / type
```
Removed value: -"string"
```
addedInput schema / properties / groupBy / maxItems
```
Added value: +32
```

Changed6 schema fields changedv0.1.1Sep 30, 2026

changedInput schema / properties / match / properties / integrations / items / enum

Previous value: -[
-  "AIRBYTE_CLOUD",
-  "AIRBYTE_SERVER",
-  "AIRFLOW",
-  "ARCH",
-  "ALTERYX_SERVER",
-  "ANTHROPIC",
-  "AWS_EC2",
-  "AWS_ECS",
-  "AWS_EMR",
-  "AWS_EKS",
-  "AWS_FIREHOSE",
-  "AWS_GLUE",
-  "AWS_LAMBDA",
-  "AWS_RDS",
-  "AWS_REDSHIFT",
-  "AWS_S3",
-  "AWS_BEDROCK",
-  "AWS_SAGEMAKER",
-  "AWS_SECRETS_MANAGER",
-  "AWS_SES",
-  "AWS_STEP_FUNCTIONS",
-  "AZURE",
-  "AZURE_CONTAINER_APPS",
-  "AZURE_DATA_FACTORY",
-  "AZURE_DATA_LAKE_STORAGE",
-  "AZURE_KEY_VAULT",
-  "AZURE_KUBERNETES_SERVICE",
-  "AZURE_LOGIC_APPS",
-  "AZURE_SYNAPSE_ANALYTICS",
-  "AZURE_VM",
-  "BAUPLAN",
-  "BOOMI",
-  "CDATA",
-  "CENSUS",
-  "CLICKHOUSE",
-  "COALESCE",
-  "COUNT",
-  "DATADOG",
-  "DATABRICKS",
-  "DATAPROC",
-  "DATAZEN",
-  "DBT",
-  "DBT_CORE",
-  "DLT",
-  "DOMO",
-  "DREMIO",
-  "DUCKDB",
-  "EMAIL",
-  "ESTUARY",
-  "ETLEAP",
-  "FABRIC",
-  "FABRIC_SYNAPSE",
-  "FIVETRAN",
-  "FORTRA",
-  "GCP_BIG_QUERY",
-  "GCP_CLOUD_RUN",
-  "GCP_CLOUD_FUNCTIONS",
-  "GCP_CLOUD_STORAGE",
-  "GCP_DATAFLOW",
-  "GCP_DATAFORM",
-  "GCP_DATASTREAM",
-  "GCP_LOOKER",
-  "GKE",
-  "GITHUB_ACTIONS",
-  "GOOGLE_CLOUD",
-  "HEVO",
-  "HEX",
-  "HIGHTOUCH",
-  "HTTP",
-  "HUBSPOT",
-  "INFORMATICA_IICS",
-  "INFORMATICA_POWERCENTER",
-  "KAFKA",
-  "KEBOOLA",
-  "KLEENE",
-  "LIGHTDASH",
-  "LINUX_SSH",
-  "MATILLION",
-  "MATILLION_ETL",
-  "METAPLANE",
-  "MICROSOFT_TEAMS",
-  "MICROSTRATEGY",
-  "MONGODB",
-  "MOTHERDUCK",
-  "MYSQL",
-  "N8N",
-  "NIMBLE",
-  "NOTION",
-  "OMNI",
-  "OPEN_AI",
-  "ORCHESTRA",
-  "PARADIME",
-  "PAGER_DUTY",
-  "PINECONE",
-  "PORTABLE",
-  "POSTGRES",
-  "POWER_AUTOMATE",
-  "POWER_BI",
-  "PREFECT_CLOUD",
-  "PYTHON",
-  "QLIK",
-  "QLIK_REPLICATE",
-  "QUICKBOOKS",
-  "RENDER",
-  "RIVERY",
-  "RUDDERSTACK",
-  "SALESFORCE",
-  "SAP",
-  "SFTP",
-  "SHAREPOINT",
-  "SIGMA",
-  "SISENSE",
-  "SLACK",
-  "SNOWFLAKE",
-  "SNOWPLOW",
-  "SODA",
-  "SQL_MESH",
-  "SQL_SERVER",
-  "STITCH",
-  "STREAMKAP",
-  "TABLEAU_CLOUD",
-  "TALEND_CLOUD",
-  "THOUGHTSPOT",
-  "TOBIKO_CLOUD",
-  "WEAVIATE",
-  "WEBHOOK",
-  "WELD",
-  "WINDOWS_SSH"
-]New value: +[
+  "AIRBYTE_CLOUD",
+  "AIRBYTE_SERVER",
+  "AIRFLOW",
+  "ARCH",
+  "ALTERYX_SERVER",
+  "ANTHROPIC",
+  "AWS_EC2",
+  "AWS_ECS",
+  "AWS_EMR",
+  "AWS_EKS",
+  "AWS_FIREHOSE",
+  "AWS_GLUE",
+  "AWS_LAMBDA",
+  "AWS_RDS",
+  "AWS_REDSHIFT",
+  "AWS_S3",
+  "AWS_BEDROCK",
+  "AWS_SAGEMAKER",
+  "AWS_SECRETS_MANAGER",
+  "AWS_SES",
+  "AWS_STEP_FUNCTIONS",
+  "AZURE",
+  "AZURE_CONTAINER_APPS",
+  "AZURE_DATA_FACTORY",
+  "AZURE_DATA_LAKE_STORAGE",
+  "AZURE_KEY_VAULT",
+  "AZURE_KUBERNETES_SERVICE",
+  "AZURE_LOGIC_APPS",
+  "AZURE_SYNAPSE_ANALYTICS",
+  "AZURE_VM",
+  "BAUPLAN",
+  "BOOMI",
+  "CDATA",
+  "CENSUS",
+  "CLICKHOUSE",
+  "COALESCE",
+  "COUNT",
+  "DATADOG",
+  "DATABRICKS",
+  "DATAPROC",
+  "DATAZEN",
+  "DBT",
+  "DBT_CORE",
+  "DLT",
+  "DOMO",
+  "DREMIO",
+  "DUCKDB",
+  "EMAIL",
+  "ESTUARY",
+  "ETLEAP",
+  "FABRIC",
+  "FABRIC_SYNAPSE",
+  "FIVETRAN",
+  "FORTRA",
+  "GCP_BIG_QUERY",
+  "GCP_CLOUD_RUN",
+  "GCP_CLOUD_FUNCTIONS",
+  "GCP_CLOUD_STORAGE",
+  "GCP_DATAFLOW",
+  "GCP_DATAFORM",
+  "GCP_DATASTREAM",
+  "GCP_LOOKER",
+  "GKE",
+  "GITHUB_ACTIONS",
+  "GOOGLE_CLOUD",
+  "HEVO",
+  "HEX",
+  "HIGHTOUCH",
+  "HTTP",
+  "HUBSPOT",
+  "INFORMATICA_IICS",
+  "INFORMATICA_POWERCENTER",
+  "KAFKA",
+  "KEBOOLA",
+  "KLEENE",
+  "LIGHTDASH",
+  "LINUX_SSH",
+  "MARIADB",
+  "MATILLION",
+  "MATILLION_ETL",
+  "METAPLANE",
+  "MICROSOFT_TEAMS",
+  "MICROSTRATEGY",
+  "MONGODB",
+  "MOTHERDUCK",
+  "MYSQL",
+  "N8N",
+  "NIMBLE",
+  "NOTION",
+  "OMNI",
+  "OPEN_AI",
+  "ORCHESTRA",
+  "PARADIME",
+  "PAGER_DUTY",
+  "PINECONE",
+  "PORTABLE",
+  "POSTGRES",
+  "POWER_AUTOMATE",
+  "POWER_BI",
+  "PREFECT_CLOUD",
+  "PYTHON",
+  "QLIK",
+  "QLIK_REPLICATE",
+  "QUICKBOOKS",
+  "RENDER",
+  "RIVERY",
+  "RUDDERSTACK",
+  "SALESFORCE",
+  "SAP",
+  "SFTP",
+  "SHAREPOINT",
+  "SIGMA",
+  "SISENSE",
+  "SLACK",
+  "SNOWFLAKE",
+  "SNOWPLOW",
+  "SODA",
+  "SQL_MESH",
+  "SQL_SERVER",
+  "STITCH",
+  "STREAMKAP",
+  "TABLEAU_CLOUD",
+  "TALEND_CLOUD",
+  "THOUGHTSPOT",
+  "TOBIKO_CLOUD",
+  "WEAVIATE",
+  "WEBHOOK",
+  "WELD",
+  "WINDOWS_SSH"
+]

addedInput schema / properties / match / properties / labels

Added value: +{
+  "additionalProperties": {
+    "items": {
+      "additionalProperties": false,
+      "description": "One place on an event body a label is read from, and the values that match there.",
+      "properties": {
+        "path": {
+          "type": "string"
+        },
+        "values": {
+          "items": {
+            "type": "string"
+          },
+          "minItems": 1,
+          "type": "array"
+        }
+      },
+      "required": [
+        "path",
+        "values"
+      ],
+      "type": "object"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  "maxProperties": 32,
+  "propertyNames": {
+    "maxLength": 64,
+    "minLength": 1,
+    "pattern": "^[a-zA-Z0-9_.:/-]+$",
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / order / anyOf

Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / order / default
```
Removed value: -0
```
removedInput schema / properties / order / type
```
Removed value: -"integer"
```

removedInput schema / properties / window

Removed value: -{
-  "anyOf": [
-    {
-      "format": "duration",
-      "gt": "PT0S",
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

First observedv0.1.0Sep 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations only give readOnlyHint=false and destructiveHint=false. The description adds genuinely useful behavior the annotations lack: omitted fields reset to defaults (not preserved), with `order` as the sole exception. This is the key hazard of a PUT-style tool and it is disclosed clearly.

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?

Two tightly written sentences, zero waste, and the most consequential fact (replace-and-reset semantics) is front-loaded.

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?

An output schema exists so return values need no explanation, and the destructive replacement behavior is covered. It does not address auth/account scoping (delegated to the X-Orchestra-Account-Id param description) or the merge-vs-replace impact on nested objects, but is largely complete for a mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 40% across 10 nested params, so the schema does not carry the burden alone. The description explains omission/default behavior generically and singles out `order`, which is valuable, but adds no meaning for name, match, groupBy, action, trigger, etc.

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 combination ('Replace a monitor's definition'), and the replacement semantics make it clearly distinct from create_monitor/get_monitor. It stops short of naming a sibling tool, but the operation is unambiguous.

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?

Replacement semantics imply this is for overwriting an existing monitor, but there is no explicit when-to-use / when-not guidance and no routing to siblings like create_monitor or reorder_monitors. Usage is inferable rather than stated.

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

Deploy Server