Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Stop alerting for a check and resolve an incident

vs_incidents_stop_alerting
DestructiveIdempotent

Turn off the check that opened an incident for its site, then mark the incident resolved. Not offered for outages or possible malware. 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_stop_alerting"
  }
}

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.1/5.0
Behavior5/5

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

Annotations declare destructive/openWorld/idempotent, and the description goes further: it names the exact side effects (check turned off, incident marked resolved, alert channels and status page subscribers notified), gives the opt-out via notify=false, and states the extra permission needed. That is what an agent needs before committing a destructive call.

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?

Three short sentences, front-loaded with the action, then the exclusion, then the permission, then the notification consequence. No filler; each sentence carries distinct information.

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 three-parameter tool with no output schema, the description covers purpose, exclusions, permission, and external side effects. It could note what is returned or point to vs_incidents_resolve_options for the partial-resolution case, but nothing essential is missing.

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 coverage is 100% and every parameter (id, notify, actionId) is documented inline, so the schema already carries the semantics. The description only restates the notify behavior, adding no syntax or edge-case detail beyond the schema.

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?

States a concrete compound action: turn off the check that opened the incident, then mark the incident resolved. This differentiates it from vs_incidents_mark_resolved by scope (it also disables the check), though it never names that sibling, so the agent must infer the boundary.

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?

"Not offered for outages or possible malware" is an explicit exclusion, and the monitors:write requirement tells the agent when it will fail. It stops short of naming the alternative tool to use for outages or when only resolution without disabling the check is wanted.

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