OneUptime

List Monitor Status Events

list_monitor_status_events

Read-only

List Monitor Status Events, with the total count.

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_monitor_status_events"
  }
}

Input Schema

Name	Required	Description
`skip`	No
`sort`	No	For example {"createdAt":"DESC"}.
`limit`	No	Default: 10, maximum: 100.
`query`	No	A field's value, or an operator such as {"_type":"GreaterThan","value":...}. Fields and operators: oneuptime_describe_resource.
`select`	No	Omit for all but statusChangeLog.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 6, 2026

changedInput schema / properties / limit / description

Previous value: -"Records to return. Default: 10, maximum: 100."New value: +"Default: 10, maximum: 100."

changedInput schema / properties / query / description

Previous value: -"Filter. Each field takes a value (exact match) or an operator, such as {\"_type\":\"GreaterThan\",\"value\":...}. Fields and operators: oneuptime_describe_resource."New value: +"A field's value, or an operator such as {\"_type\":\"GreaterThan\",\"value\":...}. Fields and operators: oneuptime_describe_resource."

changedInput schema / properties / select / description

Previous value: -"Field names to return. Omit for all but these large fields: statusChangeLog."New value: +"Omit for all but statusChangeLog."

removedInput schema / properties / skip / description
```
Removed value: -"Records to skip. Default: 0."
```

changedInput schema / properties / sort / description

Previous value: -"Fields to sort by. Example: {\"createdAt\":\"DESC\"}."New value: +"For example {\"createdAt\":\"DESC\"}."

Changed9 schema fields changedNov 4, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of records to return. Default: 10, Maximum: 100."New value: +"Records to return. Default: 10, maximum: 100."

changedInput schema / properties / query / additionalProperties
```
Previous value: -falseNew value: +true
```

changedInput schema / properties / query / description

Previous value: -"Filter criteria for Monitor Status Events. Each field accepts a direct value (exact match) or an operator object {\"_type\": \"<Operator>\", \"value\": ...}. Operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween (numbers/dates), Search (partial text), Includes (array of values). Example — items from the last 24 hours: {\"createdAt\": {\"_type\": \"GreaterThan\", \"value\": \"2026-01-01T00:00:00.000Z\"}}."New value: +"Filter. Each field takes a value (exact match) or an operator, such as {\"_type\":\"GreaterThan\",\"value\":...}. Fields and operators: oneuptime_describe_resource."

removedInput schema / properties / query / properties

Removed value: -{
-  "_id": {
-    "description": "Query operators for _id field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
-    },
-    "type": "object"
-  },
-  "createdAt": {
-    "description": "Query operators for createdAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
-    "example": {
-      "_type": "EqualTo",
-      "value": "2023-01-01T00:00:00.000Z"
-    },
-    "type": "object"
-  },
-  "createdByUserId": {
-    "description": "Query operators for createdByUserId field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
-    },
-    "type": "object"
-  },
-  "deletedAt": {
-    "description": "Query operators for deletedAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
-    "example": {
-      "_type": "EqualTo",
-      "value": "2023-01-01T00:00:00.000Z"
-    },
-    "type": "object"
-  },
-  "deletedByUserId": {
-    "description": "Query operators for deletedByUserId field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
-    },
-    "type": "object"
-  },
-  "endsAt": {
-    "description": "Query operators for endsAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
-    "example": {
-      "_type": "EqualTo",
-      "value": "2023-01-01T00:00:00.000Z"
-    },
-    "type": "object"
-  },
-  "isOwnerNotified": {
-    "description": "Query operators for isOwnerNotified field of type Boolean. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull",
-    "example": {
-      "_type": "EqualTo",
-      "value": true
-    },
-    "type": "object"
-  },
-  "monitorId": {
-    "description": "Query operators for monitorId field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
-    },
-    "type": "object"
-  },
-  "monitorStatusId": {
-    "description": "Query operators for monitorStatusId field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
-    },
-    "type": "object"
-  },
-  "projectId": {
-    "description": "Query operators for projectId field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
-    },
-    "type": "object"
-  },
-  "rootCause": {
-    "description": "Query operators for rootCause field of type Markdown. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Search, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "example_value_1"
-    },
-    "type": "object"
-  },
-  "startsAt": {
-    "description": "Query operators for startsAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
-    "example": {
-      "_type": "EqualTo",
-      "value": "2023-01-01T00:00:00.000Z"
-    },
-    "type": "object"
-  },
-  "statusChangeLog": {
-    "description": "Query operators for statusChangeLog field of type JSON. Supported operators: EqualTo, NotEqual, IsNull, NotNull",
-    "example": {
-      "_type": "EqualTo",
-      "value": "example_value_1"
-    },
-    "type": "object"
-  },
-  "updatedAt": {
-    "description": "Query operators for updatedAt field of type Date. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
-    "example": {
-      "_type": "EqualTo",
-      "value": "2023-01-01T00:00:00.000Z"
-    },
-    "type": "object"
-  },
-  "version": {
-    "description": "Query operators for version field of type Number. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, GreaterThan, LessThan, GreaterThanOrEqual, LessThanOrEqual, InBetween",
-    "example": {
-      "_type": "EqualTo",
-      "value": 50
-    },
-    "type": "object"
-  }
-}

changedInput schema / properties / select / description

Previous value: -"Optional: field names to return for each Monitor Status Event (e.g. [\"_id\", \"name\"]). Omit to get all readable fields. Large fields excluded by default (request explicitly if needed): statusChangeLog."New value: +"Field names to return. Omit for all but these large fields: statusChangeLog."

changedInput schema / properties / skip / description

Previous value: -"Number of records to skip for pagination. Default: 0. Example: skip=10 to start from the 11th record."New value: +"Records to skip. Default: 0."

changedInput schema / properties / sort / additionalProperties

Previous value: -falseNew value: +{
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}

changedInput schema / properties / sort / description

Previous value: -"Sort order for results. Use \"ASC\" for ascending or \"DESC\" for descending. Example: {\"createdAt\": \"DESC\"} to sort by newest first."New value: +"Fields to sort by. Example: {\"createdAt\":\"DESC\"}."

removedInput schema / properties / sort / properties

Removed value: -{
-  "_id": {
-    "description": "Sort order for _id field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  },
-  "createdAt": {
-    "description": "Sort order for createdAt field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  },
-  "createdByUserId": {
-    "description": "Sort order for createdByUserId field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  },
-  "deletedAt": {
-    "description": "Sort order for deletedAt field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  },
-  "deletedByUserId": {
-    "description": "Sort order for deletedByUserId field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  },
-  "endsAt": {
-    "description": "Sort order for endsAt field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  },
-  "isOwnerNotified": {
-    "description": "Sort order for isOwnerNotified field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  },
-  "monitorId": {
-    "description": "Sort order for monitorId field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  },
-  "monitorStatusId": {
-    "description": "Sort order for monitorStatusId field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  },
-  "projectId": {
-    "description": "Sort order for projectId field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  },
-  "startsAt": {
-    "description": "Sort order for startsAt field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  },
-  "updatedAt": {
-    "description": "Sort order for updatedAt field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  },
-  "version": {
-    "description": "Sort order for version field",
-    "enum": [
-      "ASC",
-      "DESC"
-    ],
-    "example": "ASC",
-    "type": "string"
-  }
-}

First observedOct 19, 2026

TDQS

C2.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that results come with a total count, but says nothing about default ordering, pagination behavior, or how the count relates to skip/limit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding and the one substantive fact (total count) is front-loaded. However, its brevity reflects under-specification rather than disciplined economy.

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?

With five optional parameters, nested query/sort/select objects, and no output schema, the description is far too thin. An agent gets no sense of the result shape beyond a total count or how to page through large event sets.

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 80%, so the schema already explains sort, limit defaults, query operators and select semantics. The description contributes nothing beyond that baseline, so a 3 is the ceiling under the rubric.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description "List Monitor Status Events, with the total count" restates the tool name and title with only the addition of a response-shape note. It does not distinguish this tool from near-identical siblings such as list_monitor_statuses or count_monitor_status_events.

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?

There is no guidance on when to use this versus list_monitor_statuses, get_monitor_status_event, or count_monitor_status_events. No filtering or pagination context is given, so the agent must infer everything from the schema alone.

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

All OneUptime tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.