Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Delete a monitor

vs_monitors_delete
DestructiveIdempotent

Delete a monitor. It stops checking at once and leaves every status page. Deleted monitors can be restored for a limited time.

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

Input Schema

NameRequiredDescriptionDefault
idYesMonitor id.

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?

Annotations already flag destructiveHint=true and idempotentHint=true. The description adds meaningful consequences beyond annotations: checking stops immediately, the monitor leaves every status page, and restoration is available only for a limited time. It does not cover permissions or the exact restore window.

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 operation and its effects. Every sentence adds useful information with no redundancy.

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 one-parameter destructive tool with annotations and no output schema, the description covers the key effects and reversibility. A minor gap is that it does not name vs_monitors_restore or specify the restore window.

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?

There is one parameter, id, and schema coverage is 100% with 'Monitor id' documented in the schema. The description adds no additional syntax or meaning for the parameter, so the baseline 3 is appropriate.

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?

Names a specific verb and resource: 'Delete a monitor.' The added effects (stops checking, leaves every status page) clarify scope, though it does not explicitly contrast with pause/restore siblings to earn a full 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?

The description implies deletion is temporary because monitors 'can be restored for a limited time,' but it never explicitly says when to use pause or restore instead of delete. Usage context is present but not fully directive.

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