Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Change an alert channel

vs_channels_update
DestructiveIdempotent

Rename an alert channel, turn it on or off, choose which alerts it gets, or change its email recipients or WhatsApp numbers. Send only the fields to change. New email recipients get a confirmation email.

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

Input Schema

NameRequiredDescriptionDefault
idYesAlert channel id.
nameNoDisplay name (up to 100 characters).
configNoWhere to send: { recipients } for EMAIL, { phoneNumbers } for WHATSAPP. On update, only the keys sent change. Secret settings of other channel types are entered in the dashboard.
enabledNofalse stops alerts going to this channel.
isDefaultNotrue adds this channel to new monitors automatically.
alertTypesNoWhich alerts this channel gets: any of DOWNTIME, SLOW_RESPONSE, VISUAL, PERFORMANCE, SSL, DNS, DOMAIN, CONTENT. An empty list gets every type except PERFORMANCE, which a channel gets only when listed.

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 declare destructiveHint=true, idempotentHint=true and openWorldHint=true, and the description adds genuinely new behavioral facts: partial-send semantics and the side effect that new email recipients receive a confirmation email. It does not explain the destructive dimension that the annotation flags — that sending a recipients/phoneNumbers list replaces the existing set.

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 the set of changeable fields, then the invocation rule and side effect. No filler or restatement of the schema.

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 nested-object mutation tool with no output schema and full schema documentation, this covers what can change, how to send changes, and a user-visible side effect. The one meaningful gap is whether array fields replace or merge with existing values, which matters given destructiveHint=true.

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%, including nested config field docs and the empty-alertTypes rule, so the schema carries the parameter burden. The description only reinforces the patch semantics and one side effect; it adds no format or constraint detail beyond the schema, so baseline 3 applies.

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 the resource (alert channel) and enumerates the concrete mutations: rename, enable/disable, alert-type selection, email recipients, WhatsApp numbers. That makes it unmistakably the partial-update operation among the vs_channels_* family (create/get/list/delete/test), though it never names a sibling explicitly.

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?

"Send only the fields to change" clearly establishes this as a patch-style update of an existing channel, which is the key usage condition separating it from vs_channels_create. It stops short of naming alternatives or stating exclusions (e.g., what to use for secret config types, or how to add a channel).

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