Skip to main content
Glama
VisualSentinel

Visual Sentinel MCP Server

Official

vs_incidents_list

List incidents for your organization, filtering by status, monitor, or paginating results.

Instructions

List incidents for the authenticated organization. Filter by status (OPEN/RESOLVED), monitor id, or paginate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoOPEN or RESOLVED.
monitorIdNoFilter to one monitor.
pageNo
limitNoDefault 50, max 200.

Implementation Reference

  • The handler function that executes the vs_incidents_list tool logic. It sends a GET request to /api/incidents with optional query parameters (status, monitorId, page, limit).
    handler: async (args, client) =>
      client.request('GET', '/api/incidents', {
        query: {
          status: pickString(args, 'status'),
          monitorId: pickString(args, 'monitorId'),
          page: pickNumber(args, 'page'),
          limit: pickNumber(args, 'limit'),
        },
      }),
  • Input schema definition for vs_incidents_list. Accepts optional status, monitorId, page, and limit fields.
    inputSchema: {
      type: 'object',
      properties: {
        status: { ...STR, description: 'OPEN or RESOLVED.' },
        monitorId: { ...STR, description: 'Filter to one monitor.' },
        page: { ...INT },
        limit: { ...INT, description: 'Default 50, max 200.' },
      },
      additionalProperties: false,
    },
  • src/tools.ts:282-306 (registration)
    Tool registration entry in the TOOLS array. Named 'vs_incidents_list', requires authentication, defined in src/tools.ts.
    {
      name: 'vs_incidents_list',
      description:
        'List incidents for the authenticated organization. Filter by status (OPEN/RESOLVED), monitor id, or paginate.',
      inputSchema: {
        type: 'object',
        properties: {
          status: { ...STR, description: 'OPEN or RESOLVED.' },
          monitorId: { ...STR, description: 'Filter to one monitor.' },
          page: { ...INT },
          limit: { ...INT, description: 'Default 50, max 200.' },
        },
        additionalProperties: false,
      },
      requiresAuth: true,
      handler: async (args, client) =>
        client.request('GET', '/api/incidents', {
          query: {
            status: pickString(args, 'status'),
            monitorId: pickString(args, 'monitorId'),
            page: pickNumber(args, 'page'),
            limit: pickNumber(args, 'limit'),
          },
        }),
    },
  • Helper function pickString used to safely extract optional string parameters from the tool arguments.
    function pickString(args: Record<string, unknown>, key: string): string | undefined {
      const v = args[key];
      return typeof v === 'string' && v.length > 0 ? v : undefined;
    }
  • Helper function pickNumber used to safely extract optional numeric parameters from the tool arguments.
    function pickNumber(args: Record<string, unknown>, key: string): number | undefined {
      const v = args[key];
      return typeof v === 'number' && Number.isFinite(v) ? v : undefined;
    }
Behavior3/5

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

With no annotations, the description carries full burden. It reveals the operation is read-only (list) and scoped to the authenticated organization, but does not disclose authentication requirements, rate limits, or side effects beyond the implied non-destructive nature.

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, front-loaded sentence that states the primary action and then lists filters efficiently. Every word serves a purpose with no redundancy or unnecessary detail.

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

Completeness2/5

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

Given no output schema, the description should explain the response format, pagination behavior, or error conditions. It only covers input filters, leaving the agent uninformed about what the tool returns and how to interpret the output, which is a significant gap for a list operation.

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 high (75%), and the description mostly echoes schema descriptions for status, monitorId, and limit. It adds the pagination concept but does not provide new meaning beyond what the schema already conveys, 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 tool lists incidents for the authenticated organization, using a specific verb+resource. It distinguishes from siblings like vs_incidents_get (single incident) and vs_alerts_list (different resource) by focusing on list behavior and available filters.

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 usage context (listing incidents with filters) but does not explicitly state when to use this tool versus alternatives like vs_incidents_get or vs_alerts_list, nor does it provide when-not or prerequisite conditions.

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