Skip to main content
Glama
VisualSentinel

Visual Sentinel MCP Server

Official

vs_monitors_check_now

Immediately trigger a monitor check and receive the fresh result, complementing the scheduled cadence.

Instructions

Trigger an immediate check for a monitor (in addition to its scheduled cadence). Returns the freshly-collected check result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMonitor id.

Implementation Reference

  • The handler function that triggers an immediate check for a monitor by sending a POST request to /api/monitors/{id}/check
      handler: async (args, client) =>
        client.request('POST', `/api/monitors/${encodeURIComponent(requireString(args, 'id'))}/check`),
    },
  • Input schema for vs_monitors_check_now: requires a string 'id' parameter
    inputSchema: {
      type: 'object',
      properties: {
        id: { ...STR, description: 'Monitor id.' },
      },
      required: ['id'],
      additionalProperties: false,
    },
  • src/tools.ts:242-257 (registration)
    Tool registration entry in the TOOLS array with name, description, schema, auth requirement, and handler
    {
      name: 'vs_monitors_check_now',
      description:
        'Trigger an immediate check for a monitor (in addition to its scheduled cadence). Returns the freshly-collected check result.',
      inputSchema: {
        type: 'object',
        properties: {
          id: { ...STR, description: 'Monitor id.' },
        },
        required: ['id'],
        additionalProperties: false,
      },
      requiresAuth: true,
      handler: async (args, client) =>
        client.request('POST', `/api/monitors/${encodeURIComponent(requireString(args, 'id'))}/check`),
    },
  • Helper function that validates and extracts a required string argument from the input args
    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;
    }
  • Core HTTP client request method used by the handler to POST to the API endpoint
      async request<T = unknown>(
        method: 'GET' | 'POST' | 'PUT' | 'PATCH' | 'DELETE',
        path: string,
        options: { query?: Record<string, string | number | boolean | undefined>; body?: unknown; auth?: boolean } = {},
      ): Promise<T> {
        const auth = options.auth ?? true;
        if (auth && !this.hasApiKey()) {
          throw new VsApiError(
            'Visual Sentinel API key required. Set VS_API_KEY (https://visualsentinel.com/settings/api-keys).',
            401,
            null,
          );
        }
    
        const url = new URL(path.startsWith('/') ? path : `/${path}`, this.baseUrl);
        if (options.query) {
          for (const [k, v] of Object.entries(options.query)) {
            if (v !== undefined && v !== null) url.searchParams.set(k, String(v));
          }
        }
    
        const headers: Record<string, string> = {
          Accept: 'application/json',
          'User-Agent': this.userAgent,
        };
        if (auth && this.apiKey) headers['X-API-Key'] = this.apiKey;
        if (options.body !== undefined) headers['Content-Type'] = 'application/json';
    
        const res = await fetch(url, {
          method,
          headers,
          body: options.body !== undefined ? JSON.stringify(options.body) : undefined,
        });
    
        const text = await res.text();
        let parsed: unknown = null;
        if (text.length > 0) {
          try {
            parsed = JSON.parse(text);
          } catch {
            parsed = text;
          }
        }
    
        if (!res.ok) {
          throw new VsApiError(
            `Visual Sentinel API ${method} ${path} returned ${res.status}`,
            res.status,
            parsed,
          );
        }
    
        return parsed as T;
      }
    }
Behavior3/5

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

Indicates mutation (trigger check) and synchronous return of result, but lacks details on side effects, error handling, or rate limits. No annotations provided to compensate.

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?

Single sentence with 15 words, no fluff. Efficiently conveys the core purpose and behavior.

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?

Given simple tool with one param and no output schema, description adequately covers action and return. Could mention potential error states but not critical.

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 has 100% coverage with a clear description of the 'id' parameter. Description adds no additional semantic information beyond what schema provides.

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?

Clearly states action (trigger immediate check), resource (monitor), and return value (freshly-collected check result). Distinguishes from siblings by specifying 'in addition to its scheduled cadence'.

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?

Provides context for on-demand checks beyond scheduled cadence, but does not explicitly state when to use vs alternatives like vs_monitors_get.

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