Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Change a monitor's basic settings

vs_monitors_update_basics
DestructiveIdempotent

Change a monitor's name, note, address, type and API settings (such as a GraphQL query), check interval, timeout, check regions or tags, or pause and resume it. Only the fields sent change.

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

Input Schema

NameRequiredDescriptionDefault
idYesMonitor id.
urlNoAddress to watch, including https://.
nameNoDisplay name.
tagsNoLabels used to group monitors (status page groups can follow tags).
typeNoMonitor type: HTTP, HTTPS, TCP, PING, DNS, SSL, WEBSOCKET or GRAPHQL. Switching to GRAPHQL needs a query in apiConfig unless the monitor already has one saved.
enabledNofalse pauses all checks and alerts, true resumes them.
timeoutNoMilliseconds to wait for the site before a check fails (1000 to 120000).
apiConfigNoSettings of an API or GraphQL monitor, such as the GraphQL query or checks on the JSON response (refused for other monitor types). The whole set is replaced: settings left out return to their defaults. null clears them.
locationsNoCheck regions: any of EU, US, ASIA (Europe, United States, Asia Pacific). Your plan sets which regions this workspace can use.
descriptionNoShort note about the site (up to 500 characters).
checkIntervalNoSeconds between uptime checks (30 to 86400). Your plan sets the shortest interval allowed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds the partial-update rule ('Only the fields sent change'), which is genuine behavioral context not in the annotations. It does not, however, warn about the destructive edges — e.g. that apiConfig is replaced wholesale so omitted settings reset, or that enabled=false silently stops all checks and alerts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tightly packed sentence with the partial-update rule front-loaded immediately after the scope list. Dense but every enumerated item earns its place by delineating scope from sibling update tools; no filler or repetition.

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 an 11-parameter destructive mutation with no output schema, the description plus rich schema and annotations cover the essentials: what changes, partial-update behavior, and safety hints. Missing is any note on permissions/plan constraints (schema mentions plans but the description does not) and no statement of what the call returns or how failures surface.

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 every parameter carries its own description, including enum values, ranges, and the apiConfig replacement semantics. The description only restates field names at a high level ('such as a GraphQL query'), adding no syntax or format meaning beyond the schema, so the 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?

States a specific verb and resource ('Change a monitor's...') and enumerates exactly which settings fall in scope: name, note, address, type, API settings, interval, timeout, regions, tags, pause/resume. That enumeration implicitly delineates it from the many vs_monitors_update_* siblings (check method, alerting, content, expectations, performance, headers, etc.), but it never names an alternative explicitly, so it stops short of a 5.

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?

'Only the fields sent change' tells the agent this is a partial update, which is real usage guidance. However, there is no explicit when-to-use vs when-not guidance and no routing to sibling tools such as vs_monitors_update_check_method or vs_monitors_pause, leaving the agent to infer boundaries from the field list.

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