Skip to main content
Glama
VisualSentinel

Visual Sentinel MCP Server

Official

vs_monitors_get

Retrieve detailed information for a specific monitor, including current status, last check, and configuration.

Instructions

Fetch a single monitor by id, including its current status, last check, and configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMonitor id (cuid).

Implementation Reference

  • The handler function for 'vs_monitors_get'. It extracts the 'id' argument and makes a GET request to /api/monitors/{id}.
      handler: async (args, client) =>
        client.request('GET', `/api/monitors/${encodeURIComponent(requireString(args, 'id'))}`),
    },
  • Input schema for 'vs_monitors_get': requires a string 'id' (monitor id, cuid format).
    inputSchema: {
      type: 'object',
      properties: {
        id: { ...STR, description: 'Monitor id (cuid).' },
      },
      required: ['id'],
      additionalProperties: false,
    },
  • src/tools.ts:186-201 (registration)
    Full tool registration entry for 'vs_monitors_get' in the TOOLS array, with name, description, inputSchema, requiresAuth flag, and handler.
    {
      name: 'vs_monitors_get',
      description:
        'Fetch a single monitor by id, including its current status, last check, and configuration.',
      inputSchema: {
        type: 'object',
        properties: {
          id: { ...STR, description: 'Monitor id (cuid).' },
        },
        required: ['id'],
        additionalProperties: false,
      },
      requiresAuth: true,
      handler: async (args, client) =>
        client.request('GET', `/api/monitors/${encodeURIComponent(requireString(args, 'id'))}`),
    },
  • Helper function 'requireString' used by the handler to extract and validate the required 'id' 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;
    }
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It accurately describes the tool as a read operation that returns monitor details, which is sufficient for a simple fetch. No behavioral omissions or contradictions.

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?

The description is a single, well-structured sentence that conveys the core purpose and included information without any extraneous words. It is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (single parameter, no output schema), the description is complete: it states the action, the unique identifier, and the fields returned. No additional context is necessary.

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%: the single parameter 'id' is described in the schema as 'Monitor id (cuid).' The description does not add any additional meaning or clarification beyond the schema, so baseline 3 is appropriate.

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 the action: 'Fetch a single monitor by id', and specifies what is included (status, last check, configuration). This distinguishes it from siblings like vs_monitors_list (which fetches all monitors) and vs_monitors_create.

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 description implies use when needing details of a specific monitor, but does not explicitly mention when not to use it or suggest alternatives among siblings. The context is clear but lacks exclusion guidance.

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