Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Set a server's sites

vs_servers_monitors_set
DestructiveIdempotent

Choose exactly which monitors (sites) run on a server. The list replaces the current links.

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>",
      "monitorIds": "<monitorIds>"
    },
    "name": "vs_servers_monitors_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesServer id.
monitorIdsYesMonitor ids hosted on this server.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description's 'replaces the current links' usefully reinforces that existing assignments are wiped, but it stops short of saying what happens to monitors dropped from the list or what permission is needed to reassign them.

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 short sentences, front-loaded with the action and immediately followed by the replace semantic that matters for correct invocation. Nothing is wasted.

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 tool with a complete schema and full annotation coverage, and with no output schema to explain, the description says enough to call it correctly. The only meaningful gap is the consequence of removal, which an agent could infer from 'replaces'.

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%, so both parameters are already documented as 'Server id' and 'Monitor ids hosted on this server'. The description adds the synonym 'sites' for monitors, which helps terminology matching, but adds nothing about the 2000-item cap or ordering.

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 uses a specific verb-and-resource pair ('Choose exactly which monitors (sites) run on a server') and clarifies that monitors are exposed as 'sites' elsewhere. It implicitly separates the tool from the read-only vs_servers_monitors_get, but it does not name that sibling or any other related tool to draw the line 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?

'The list replaces the current links' tells the agent this is a whole-list overwrite, which implies it should not be used for incremental additions. However, the description never states when to prefer alternatives such as vs_servers_monitors_get for inspection or vs_monitors_bulk_update, and it gives no prerequisites.

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