Skip to main content
Glama
Sign In

OneUptime

by com.oneuptime
OverviewDiscussionsAdmin

Count Alert State Timelines

count_alert_state_timelines
Read-only

Count Alert State Timelines, 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_alert_state_timelines"
  }
}

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 Alert State Timelines. 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"
-  },
-  "alertId": {
-    "description": "Query operators for alertId field of type Object ID. Supported operators: EqualTo, NotEqual, IsNull, NotNull, EqualToOrNull, Includes",
-    "example": {
-      "_type": "EqualTo",
-      "value": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
-    },
-    "type": "object"
-  },
-  "alertStateId": {
-    "description": "Query operators for alertStateId 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"
-  },
-  "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"
-  },
-  "stateChangeLog": {
-    "description": "Query operators for stateChangeLog 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

C2.6/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 by structured data. The description adds only the all-versus-filtered scoping detail and says nothing about cost of a full unfiltered count, pagination, or what the numeric result represents.

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 the resource front-loaded, which is good, but the leading clause duplicates the tool title and the trailing clause is a grammatically awkward fragment. There is little waste but also little added information per word.

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 simple one-optional-parameter count tool with annotations covering safety and no output schema, the description is minimally adequate. It does not state that the return value is a numeric count rather than records, which is the one thing an agent cannot infer from the schema here.

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 optional query parameter is documented in-schema, including operator syntax and a pointer to oneuptime_describe_resource. The description's mention of "a filter matches" only loosely gestures at the same parameter, so the schema does the real work; baseline 3 applies.

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

Purpose3/5

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

"Count Alert State Timelines" names a specific verb and resource, so the core action is unambiguous, and "all or those a filter matches" indicates an optional filter. However, the first clause is essentially the title restated, and it offers no distinction from the closely named sibling list_alert_state_timelines beyond the verb itself.

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?

The phrase "all or those a filter matches" implies the query parameter is optional, which is useful, but there is no explicit guidance on when to count versus when to call list_alert_state_timelines or get_alert_state_timeline. No prerequisites or exclusions are stated.

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