Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Pause the monitor and resolve an incident

vs_incidents_pause_monitor
DestructiveIdempotent

Pause the checks and alerts of the monitor behind an outage incident, then mark the incident resolved. Offered for outages only. Needs monitors:write as well. The incident's alert channels and status page subscribers are told it is resolved unless notify is false.

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_incidents_pause_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIncident id.
notifyNofalse records the change without telling the incident's alert channels and status page subscribers (default true).
actionIdNoOptional UUID you make once per action, so a retried call is not applied or announced twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructive, non-readOnly, and idempotent, so the description's added value is the auth requirement (monitors:write) and the user-visible side effect that alert channels and status page subscribers are notified unless notify is false. It does not disclose how to reverse the pause (resume/restore) or what the call returns, which would matter for a destructive mutation.

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?

Four short sentences, front-loaded with the action and scope before prerequisites and notification behavior. No filler or repetition of the name.

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 destructive compound mutation the description covers the action, scope, auth, and notification effects, and annotations carry the safety profile. Missing is reversibility (how to un-pause) and any indication of return content, which there is no output schema to substitute for.

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 id, notify, and actionId are already fully documented; the description only restates the notify=false behavior. Baseline 3 is appropriate since the schema does the heavy lifting and the description adds no extra parameter nuance.

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 names a specific compound action (pause the monitor's checks and alerts, then mark the incident resolved) tied to a named resource, so an agent knows exactly what it does. It does not name the sibling tools it supersedes (vs_monitors_pause, vs_incidents_mark_resolved), so differentiation is only implied by 'Offered for outages only.'

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?

'Offered for outages only' gives an explicit scope restriction, and 'Needs monitors:write as well' states a prerequisite that selects or excludes callers. It stops short of naming the alternative siblings to use for non-outage incidents, leaving that inference to the agent.

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