Skip to main content
Glama
Sign In

Visual Sentinel

by com.visualsentinel
OverviewDiscussionsAdmin

Check a website

vs_website_check
Read-onlyIdempotent

Quick health check for a URL: HTTP status, response time, server header, content snippet, and basic SSL state. No authentication required. 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": {
      "url": "<url>"
    },
    "name": "vs_website_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL to test, including protocol (https://...).

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 declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: it reveals the five data points a caller will receive (which matters since there is no output schema) and states no auth is needed. It stops short of timeouts, rate limits, or failure behavior.

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 sentences, front-loaded with the purpose and the returned fields, then a precondition and a docs link. Nothing is redundant and nothing useful is buried.

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 single-parameter read-only probe with no output schema, the description is nearly complete because it enumerates the return values. The one real gap is disambiguation from the SSL, DNS, and speed-test siblings, which a caller in this 90+ tool server would need.

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?

Only one parameter exists and schema description coverage is 100%, with the schema already specifying 'Full URL to test, including protocol'. The description adds no syntax, format, or validation detail about the URL beyond that, so this sits at the high-coverage baseline.

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 ('Quick health check for a URL') and enumerates exactly what is returned: HTTP status, response time, server header, content snippet, SSL state. It is clear on its own, but it does not differentiate from siblings that overlap heavily (vs_ssl_check, vs_speed_test, vs_dns_check), so an agent must guess which check tool to pick.

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?

'Quick health check' implies the usage context, and 'No authentication required' removes a precondition, but there is no explicit when-to-use/when-not and no pointer to the overlapping alternatives such as vs_ssl_check or vs_speed_test. Usage must be inferred from the enumerated outputs.

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