Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Change workspace settings

vs_workspace_settings_update
DestructiveIdempotent

Change workspace defaults. Send alertDefaults, monitoring, or both; only the fields you send change. Needs an owner or admin account.

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

Input Schema

NameRequiredDescriptionDefault
monitoringNoslaTarget (uptime target percent, 90 to 100) and responseTimeThresholds { degraded, critical } in milliseconds.
alertDefaultsNoServer alert defaults: serverAlertEnabled, serverCpuThreshold, serverMemoryThreshold, serverDiskThreshold (percent), serverAlertDelay (seconds), serverAlertCooldown (seconds), serverConsecutiveThreshold, defaultNotificationChannelIds.

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 readOnlyHint=false; the description adds the meaningful qualifier that only submitted fields change, which tempers the destructive warning and explains the idempotency. The owner/admin requirement is also stated, which annotations cannot convey. It does not say whether omitted nested keys are preserved or reset.

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 invocation semantics, then the access prerequisite. Every sentence carries distinct information with no padding.

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 two-parameter mutation tool with a rich 100% covered schema and no output schema, the description covers action, partial-update behaviour and authorization. The one gap is how nested objects merge on partial submission, 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 description coverage is 100% and both nested objects carry their own detailed descriptions, so the description's mention of alertDefaults/monitoring adds nothing beyond the schema. Baseline 3 applies; nested merge semantics when only part of a sub-object is sent remain undocumented in both places.

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 and resource ("Change workspace defaults") and enumerates the two writable field groups (alertDefaults, monitoring), which scopes it well. It does not differentiate itself from the nearby vs_workspace_update or vs_workspace_alert_grouping_update siblings, so an agent must infer it handles only the alert/monitoring default blocks.

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 alertDefaults, monitoring, or both; only the fields you send change" gives clear patch-style invocation guidance, and "Needs an owner or admin account" states a prerequisite. It stops short of naming alternatives (e.g. vs_workspace_settings_get to inspect current values, vs_workspace_update for other workspace fields), so the when-not case is left to inference.

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