Skip to main content
Glama
VisualSentinel

Visual Sentinel MCP Server

Official

vs_website_check

Check a URL's health: HTTP status, response time, server header, content snippet, and basic SSL state. No authentication needed.

Instructions

Quick health check for a URL: HTTP status, response time, server header, content snippet, and basic SSL state. No authentication required.

Input Schema

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

Implementation Reference

  • Handler function for the vs_website_check tool. Makes a GET request to the Visual Sentinel API endpoint /api/tools/website-check with the 'url' query parameter, without authentication.
      handler: async (args, client) =>
        client.request('GET', '/api/tools/website-check', {
          auth: false,
          query: { url: requireString(args, 'url') },
        }),
    },
  • Input schema for vs_website_check: requires a single 'url' string (full URL including protocol).
    inputSchema: {
      type: 'object',
      properties: {
        url: { ...STR, description: 'Full URL to test, including protocol (https://...).' },
      },
      required: ['url'],
      additionalProperties: false,
    },
  • src/tools.ts:133-151 (registration)
    Registration of the vs_website_check tool in the TOOLS array as a public (no auth) tool with name, description, inputSchema, and handler.
    {
      name: 'vs_website_check',
      description:
        'Quick health check for a URL: HTTP status, response time, server header, content snippet, and basic SSL state. No authentication required.',
      inputSchema: {
        type: 'object',
        properties: {
          url: { ...STR, description: 'Full URL to test, including protocol (https://...).' },
        },
        required: ['url'],
        additionalProperties: false,
      },
      requiresAuth: false,
      handler: async (args, client) =>
        client.request('GET', '/api/tools/website-check', {
          auth: false,
          query: { url: requireString(args, 'url') },
        }),
    },
  • The requireString helper function used by the handler to extract and validate the required 'url' argument.
    function requireString(args: Record<string, unknown>, key: string): string {
      const v = pickString(args, key);
      if (!v) throw new Error(`Argument "${key}" (string) is required.`);
      return v;
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It notes no authentication required and lists outputs, but does not mention rate limits, timeouts, or error handling 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 purpose, no wasted words. Highly concise and efficient.

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 simple tool with one parameter and no output schema, the description adequately describes inputs and outputs. Could add return format or error behavior, but sufficient given simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers the single parameter with description; the tool's description adds context that URL must include protocol, enhancing the schema's guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it's a quick health check for a URL, listing specific outputs (HTTP status, response time, etc.). It distinguishes from siblings like vs_dns_check and vs_ssl_check by focusing on general health.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Indicates quick health check usage and that no authentication is needed. Lacks explicit when-not-to-use or alternatives, but context from sibling tools implies its role among more specific checks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VisualSentinel/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server