Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Change a monitor's check method and redirects

vs_monitors_update_check_method
DestructiveIdempotent

Choose which method this monitor's uptime check uses, and whether the check follows redirects and how many. It is a saved monitor setting the scheduled checks use. Only the fields given 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_check_method"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor id.
checkMethodNoMethod this monitor's uptime check uses: GET, POST, PUT, PATCH, DELETE, HEAD, QUERY, OPTIONS. GET unless changed.
maxRedirectsNoMost redirects to follow (0 to 10).
followRedirectsNotrue follows redirects.

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?

The description adds real context beyond the annotations: it clarifies partial-update semantics (unspecified fields are preserved) and that this is a saved configuration consumed by scheduled checks rather than an immediate check. But it does not explain the destructiveHint=true annotation, nor whether the change is immediate or pending until the next scheduled run.

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?

Three short sentences, front-loaded with what is being changed, followed by the runtime implication and the partial-update rule. No filler, though the third sentence could be merged into the first for tighter grouping.

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 4-parameter non-read-only tool with no output schema, the description covers what changes and preservation of unspecified fields. It is silent on whether changes take effect immediately versus at the next scheduled check, and does not address the destructiveHint risk profile an agent would want before mutating monitor config.

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%, with enums and min/max bounds documented for checkMethod and maxRedirects, so the schema does the heavy lifting. The description reinforces that check method and redirect count are linked settings but adds no syntax or format 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?

The description states a specific verb+resource: changing a monitor's uptime check method plus its redirect-following settings. That field-level specificity naturally distinguishes it from siblings like vs_monitors_update_basics or vs_monitors_update_performance, though no sibling is named explicitly.

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 given change' implies this is the partial-update entry point for these two settings, which is useful context. However, it never states when to prefer this tool over the adjacent update_* tools, nor whether a new check must be triggered for the change to apply.

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