VeriTeknik

Get domain monitor status

get_domain_monitor_status

Read-onlyIdempotent

Returns the live monitoring status of one domain: up/down state, monitor type, recent uptime events and SSL certificate days remaining. Parameter: customerDomainId (UUID, from list_my_domains or list_domain_monitors), optional eventLimit (number of recent events to return, default 10, max 100). up is null when the monitor has no verdict yet (pending or in maintenance) - unknown, not down - and an uptime window with no heartbeat is null, not zero. Call it when the user asks why one domain alerted, or how long its certificate has left.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customerDomainId": "<customerDomainId>"
    },
    "name": "get_domain_monitor_status"
  }
}

Input Schema

Name	Required	Description	Default
`eventLimit`	No	Number of recent events to return (default 10, max 100)
`customerDomainId`	Yes	UUID of the customer domain

Output Schema

Name	Required	Description	Default
`data`	Yes
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 8, 2026
- changedOutput schema / properties / data / properties / liveStatus / properties / up / type
```
Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / liveStatus / properties / uptime30d / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / liveStatus / properties / uptime7d / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

Changed11 schema fields changedOct 25, 2026

removedOutput schema / properties / data / properties / liveStatus / properties / certDaysRemaining / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / data / properties / liveStatus / properties / certDaysRemaining / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / data / properties / liveStatus / properties / uptime24h / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / data / properties / liveStatus / properties / uptime24h / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / data / properties / monitor / properties / currentUp / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / data / properties / monitor / properties / currentUp / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

changedOutput schema / properties / data / properties / recentEvents / items / properties / createdAt / anyOf

Previous value: -[
-  {
-    "format": "date-time",
-    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "date-time",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / data / properties / recentEvents / items / properties / durationSeconds / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / data / properties / recentEvents / items / properties / durationSeconds / type
```
Added value: +[
+  "number",
+  "null"
+]
```
removedOutput schema / properties / data / properties / recentEvents / items / properties / message / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / data / properties / recentEvents / items / properties / message / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed5 schema fields changedOct 17, 2026

removedOutput schema / properties / data / properties / monitor / properties / createdAt

Removed value: -{
-  "anyOf": [
-    {
-      "format": "date-time",
-      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedOutput schema / properties / data / properties / monitor / properties / id
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / data / properties / monitor / required

Previous value: -[
-  "id",
-  "domainName",
-  "monitorType",
-  "monitorStatus",
-  "currentUp",
-  "createdAt"
-]New value: +[
+  "domainName",
+  "monitorType",
+  "monitorStatus",
+  "currentUp"
+]

removedOutput schema / properties / data / properties / recentEvents / items / properties / id
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / data / properties / recentEvents / items / required

Previous value: -[
-  "id",
-  "eventType",
-  "message",
-  "durationSeconds",
-  "createdAt"
-]New value: +[
+  "eventType",
+  "message",
+  "durationSeconds",
+  "createdAt"
+]

First observedOct 4, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral semantics beyond them: up is null rather than false when there is no verdict (pending/maintenance), and an uptime window without a heartbeat is null, not zero. It says nothing about refresh cadence, staleness of "live" data, or permissions.

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?

Front-loaded with the purpose, then parameters, then the null caveats, then the call trigger. Every sentence carries information. The small cost is the opening field enumeration, which partly duplicates what the output schema already returns.

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?

With an output schema present, an idempotent read, and only two parameters, the description covers what an agent needs: what it returns, where the ID comes from, result limits, and the null semantics that would otherwise cause misreading of a healthy-but-unknown monitor. Only the meaning of "live" (polling interval or cache lag) is left unaddressed.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description earns more by telling the agent where customerDomainId comes from (list_my_domains or list_domain_monitors) and restating eventLimit's default and ceiling in the context of "recent events." The provenance of the UUID is meaning the schema does not carry.

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 ("Returns the live monitoring status of one domain") and enumerates the payload: up/down state, monitor type, recent uptime events, SSL days remaining. Scope ("one domain") separates it from the plural listing siblings without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives concrete trigger conditions: "when the user asks why one domain alerted, or how long its certificate has left." It also names list_my_domains and list_domain_monitors as ID sources, implicitly routing discovery there. It stops short of an explicit exclusion, e.g. telling the agent not to use get_vps_monitor_status or the list tools for single-domain detail.

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

All VeriTeknik 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.