Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Get bulk monitor metrics

vs_monitors_metrics_bulk
Read-onlyIdempotent

Fetch uptime or response-time metrics for up to 100 monitors in a single request. Use window for a preset window (1h, 6h, 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. Returns a monitors object keyed by monitor id.

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": {
      "monitorIds": "<monitorIds>",
      "metric": "<metric>"
    },
    "name": "vs_monitors_metrics_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
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`.
metricYesMetric to return: "uptime" or "response-time".
windowNoPreset window: 1h, 6h, 24h, 7d, 30d, 90d, 365d. Default 30d. Ignored when from+to or all are supplied.
monitorIdsYesList of monitor IDs to fetch metrics for (max 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds the max-100 batching constraint, the default 30d window, and the precedence rules among range selectors. It also discloses the return shape ('monitors object keyed by monitor id'), which annotations do not cover.

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-loaded with what the tool does, followed by the mutually exclusive range modes. Every clause carries operational meaning; 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?

With no output schema, the description responsibly sketches the return shape and covers defaults, limits, and mode precedence — enough to invoke correctly. It leaves open what the per-monitor metric values look like (series granularity, empty-history behavior), a minor gap for an analytics tool.

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 baseline is 3; the description goes further by explaining how `window`, `from`/`to`, and `all` interact and which wins, information that is split across individual property descriptions in the schema. Metric choices and default are restated rather than added, keeping it just below 5.

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 (Fetch) and resource (uptime or response-time metrics) with an explicit scope qualifier: up to 100 monitors in a single request. The 'bulk' + 'up to 100' framing immediately separates it from the single-monitor sibling vs_monitors_uptime without requiring schema inspection.

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?

Clearly lays out three modes of operation — preset `window`, custom `from`/`to`, or `all: true` — and states precedence ('takes precedence over from/to and window'). It stops short of naming the single-monitor alternative (vs_monitors_uptime) or when to prefer bulk over per-monitor calls, so it is not a full 5.

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