Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Change alert grouping settings

vs_workspace_alert_grouping_update
DestructiveIdempotent

Change how alerts that happen together are grouped. Send every field: any field left out goes back to its default.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vs_workspace_alert_grouping_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNoGroup related alerts (default true).
maxGroupSizeNoMost alerts in one group (5 to 200, default 50).
groupByRootCauseNoGroup alerts with the same likely cause (default true).
timeWindowMinutesNoMinutes alerts must fall within to be grouped (5 to 60, default 15).
suppressDuplicatesNoHold back repeated identical alerts (default true).
similarityThresholdNoHow alike alerts must be to group, 0.5 to 0.95 (default 0.7).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The reset-on-omission behavior is exactly the kind of context annotations cannot convey, and it explains why destructiveHint=true despite an 'update' name. It does not say the setting is workspace-wide or that grouping affects alert volume/delivery for all monitors, which would have completed the picture.

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, both load-bearing; the purpose comes first and the destructive caveat immediately follows. Nothing is redundant with the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, zero-required, destructive mutation with no output schema, the description covers the reset hazard but omits the obvious prerequisite of fetching current values first and the scope of the change. An agent could call it correctly but would likely clobber settings it never read.

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% with ranges and defaults spelled out per parameter, so the baseline is 3. The description adds cross-parameter semantics the schema lacks: every field is effectively required because omissions silently revert to defaults. That is real added meaning beyond structured data.

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 specific verb ('Change') and resource ('how alerts that happen together are grouped'), which clearly maps to the alert-grouping settings and is distinguishable from vs_workspace_alert_grouping_get. It stops short of naming the get sibling as the read counterpart, so sibling differentiation is implied rather than explicit.

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?

'Send every field: any field left out goes back to its default' is a valuable invocation rule, but it addresses how to call rather than when to call. There is no guidance to read current settings via vs_workspace_alert_grouping_get first, and no exclusions about when this should not be used.

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