Skip to main content
Glama
Sign In

OneUptime

by com.oneuptime
OverviewDiscussionsAdmin

Count Monitor Status Events

count_monitor_status_events
Read-only

Count Monitor Status Events, all or those a filter matches.

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": "count_monitor_status_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoA field's value, or an operator such as {"_type":"GreaterThan","value":...}. Fields and operators: oneuptime_describe_resource.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed3 schema fields changed
    • changedInput schema / properties / query / additionalProperties
      Previous value: -falseNew value: +true
    • changedInput schema / properties / query / description
      Previous value: -"Optional filter criteria. If omitted, counts all 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"
-  }
-}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare a safe, closed-world read operation (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description only needs supporting context. It adds that the scope is the full set by default, but says nothing about what is returned (a numeric count) or how filters affect the total.

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

Conciseness4/5

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

One short sentence with the resource scope front-loaded and no filler. The phrasing "all or those a filter matches" is slightly clipped but costs no space that matters.

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

Completeness3/5

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

For a low-complexity, one-optional-parameter tool with full schema coverage, this is nearly sufficient. The notable remaining gap is that with no output schema present, the description never states that the result is a count value, leaving the return shape to inference.

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 100% and the single query parameter is fully documented in the schema, including operator syntax and a pointer to oneuptime_describe_resource. The description only restates that the filter is optional, so baseline 3 applies.

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?

The description pairs a specific verb ("Count") with a specific resource ("Monitor Status Events"), so the operation is unambiguous. It does not explicitly contrast itself with the closely named sibling list_monitor_status_events, which keeps it below 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 Guidelines3/5

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

"All or those a filter matches" implies the query parameter is optional and that unfiltered counting is supported, which is useful context. However, there is no explicit guidance on when to pick this over count_monitors, count_monitor_statuses, or list_monitor_status_events.

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

All OneUptime toolsInspect
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.

Resources