Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Get monitor uptime

vs_monitors_uptime
Read-onlyIdempotent

Fetch the uptime percentage and time-series breakdown for a monitor. Use window for a preset window (24h, 7d, 30d, 90d, 365d; default 30d), supply both from and to (ISO 8601) for a custom date range, or set all: true for the full available history.

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": {
      "id": "<id>"
    },
    "name": "vs_monitors_uptime"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor id.
toNoISO 8601 end of a custom range. Must be supplied with `from`.
allNoReturn the full available history from the earliest stored data. Takes precedence over from/to and window.
fromNoISO 8601 start of a custom range (e.g. 2026-01-01T00:00:00Z). Must be supplied with `to`.
windowNoPreset window: 1h, 6h, 24h, 7d, 30d, 90d, 365d. Default 30d. Ignored when from+to or all are supplied.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the return content (uptime percentage and time-series breakdown) and the default window, but does not disclose pagination, rate limits, or other behavioral details.

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 front-load the purpose, then compactly explain the three date-range modes. Every clause serves a clear function, with no filler.

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 read-only metrics tool with full schema coverage and safety annotations, the description covers what is returned and how to select a time range. It would be stronger if it explicitly distinguished this tool from sibling monitor/mets tools, but it is otherwise complete enough to call correctly.

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%, so the schema already documents every parameter, including precedence and the full list of preset windows. The description reinforces mode selection but slightly under-specifies the window enum by listing only 24h, 7d, 30d, 90d, and 365d while the schema also permits 1h and 6h.

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 states a specific verb and resource: fetching uptime percentage and time-series breakdown for a monitor. It is clear what the tool returns, but it does not explicitly differentiate this from nearby siblings such as vs_monitors_get or vs_monitors_metrics_bulk.

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?

The description explains how to choose between the `window`, `from`/`to`, and `all` modes, which is useful. However, it gives no guidance on when to use this tool versus sibling tools like vs_monitors_get or vs_monitors_metrics_bulk, so tool-selection guidance is only implied.

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

All Visual Sentinel 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