Orchestra MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Update a monitor

update_monitor

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.

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

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. ``operation_failures_only`` narrows what the dimensions...
`order`	No
`action`	No	What happens to the events this monitor claimed. ``mute`` claims them and drops them, with no incident and no alert - the known-broken-thing case.
`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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv2026.10.12-0Oct 14, 2026

changedInput schema / properties / action / description

Previous value: -"What happens to the events this monitor claimed.\n\n``mute`` claims them and sends no alert - the known-broken-thing case. They are still\nrecorded, on incidents the monitor owns, so a mute is silent without being invisible."New value: +"What happens to the events this monitor claimed.\n\n``mute`` claims them and drops them, with no incident and no alert - the\nknown-broken-thing case."

changedInput schema / properties / action / properties / assignee / anyOf

Previous value: -[
-  {
-    "format": "uuid4",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / action / properties / subscribers

Added value: +{
+  "default": [],
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

changedInput schema / properties / groupBy / items / anyOf

Previous 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"
-  }
-]New 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"
+  },
+  {
+    "additionalProperties": false,
+    "description": "A place on an event body to group on. ``label`` is what the incident's name and alert\ncall the value found at ``path``.",
+    "properties": {
+      "label": {
+        "maxLength": 64,
+        "minLength": 1,
+        "pattern": "^[a-zA-Z0-9_.:/-]+$",
+        "type": "string"
+      },
+      "path": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "label",
+      "path"
+    ],
+    "type": "object"
+  }
+]

changedInput schema / properties / match / description

Previous value: -"Which events a monitor claims: AND across dimensions, OR within a list.\n\nAt least one dimension has to be given. A monitor matching every dimension by saying\nnothing would claim every event on the account, which is never what an author means."New value: +"Which events a monitor claims: AND across dimensions, OR within a list.\n\nAt least one dimension has to be given. A monitor matching every dimension by saying\nnothing would claim every event on the account, which is never what an author means.\n\n``operation_failures_only`` narrows what the dimensions..."

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",
-  "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"
-]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_BATCH",
+  "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",
+  "TYPESAFE",
+  "WEAVIATE",
+  "WEBHOOK",
+  "WELD",
+  "WINDOWS_SSH"
+]

addedInput schema / properties / match / properties / operationFailuresOnly
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
addedInput schema / properties / name / maxLength
```
Added value: +100
```

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

A4/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries most of the burden — and it delivers the single most important behavior: omitted fields reset to their defaults rather than being preserved, with `order` as the sole exception. That is exactly the detail that prevents an agent from silently wiping configuration. It stops short of disclosing permission requirements, not-found/error behavior, or concurrency, so a 4 rather than a 5.

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 sentences, zero filler. The core replacement semantics come first and the default-fallback caveat with its `order` exception follows immediately. Nothing is redundant with the title or schema.

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?

For a 10-parameter, deeply nested mutation tool with an output schema (so return values need not be explained), the description covers the decisive gotcha of full-replacement semantics. It leaves auth/permission expectations and failure modes unstated, which is a minor gap given the annotations are silent on them.

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?

With only 40% schema description coverage across 10 parameters, the description must compensate, but it only clarifies one field's semantics (`order` keeps the monitor's place). It says nothing about monitor_id, enabled, description, or the account header, and adds no meaning beyond the schema text for the nested match/action/groupBy/trigger objects.

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?

States a specific verb and resource: 'Replace a monitor's definition with the one in the body.' The word 'Replace' immediately distinguishes it from the sibling create_monitor/get_monitor/delete_monitor/reorder_monitors, and an agent can tell what the call does without opening the schema.

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?

Usage is implied by the replace semantics and by the field-default rule, which tells the caller to supply a complete definition. However, there is no explicit when-to-use guidance naming alternatives (e.g. create_monitor for new monitors), nor any stated prerequisite such as needing an existing monitor_id.

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

Deploy Server