Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Create a monitor

vs_monitors_create

Create a new monitor. Provide at least name, url, and type. Returns the created monitor including its assigned id. Docs: https://visualsentinel.com/mcp#tools

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": {
      "name": "<name>",
      "url": "<url>",
      "type": "<type>"
    },
    "name": "vs_monitors_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL to monitor (or hostname for PING/PORT/DNS/SSL).
nameYesDisplay name for the monitor.
portNoTCP port for PORT monitors. Added to the url as host:port.
typeYesMonitor type: HTTPS (default), HTTP, KEYWORD, API, GRAPHQL, WEBSOCKET, PING, PORT, TCP, UDP, DNS or SSL. Screenshot (visual) checks are a setting on a website monitor, not a type.
methodNoHTTP method for HTTP/HTTPS monitors (default GET).
keywordNoText the page must contain, for KEYWORD monitors.
timeoutNoPer-check timeout in seconds, 1 to 120 (default 30).
intervalNoCheck interval in seconds, 60 to 86400 (default 300). Raised to the plan's fastest allowed interval if lower.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=true, so the mutating, non-idempotent nature is covered structurally. The description adds only that the created object (including its id) is returned. It does not disclose whether duplicate names/URLs are rejected, what defaults (alerting, regions) are applied, or any rate/quota behavior.

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, front-loaded sentences: purpose, required inputs, return value. The trailing docs URL is mildly extraneous but provides a cheap escape hatch for detail. Nothing is buried or padded.

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?

With no output schema, the description usefully states the return contains the created monitor and its assigned id, which the agent needs for follow-up calls. Combined with 100% schema coverage for 8 params, the main remaining gap is absence of guidance on choosing the right type or handling conflicts.

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%, so each of the 8 parameters is already documented in-schema, including enum-like type values and interval/timeout ranges. The description's 'at least name, url, and type' merely restates the required array and adds no meaning beyond it, 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+resource ('Create a new monitor') and confirms the effect ('Returns the created monitor including its assigned id'). An agent can distinguish it from the many vs_monitors_update_* and vs_monitors_get siblings from the name plus description, though the description itself never names an alternative.

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?

'Provide at least name, url, and type' gives a minimal prerequisite, implying the tool is the entry point before the update_* / mute / pause siblings are used. But there is no explicit when-to-use or when-not guidance, no mention of plan limits on interval, and no pointer to which sibling to use for later configuration changes.

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