Skip to main content
Glama
VisualSentinel

Visual Sentinel MCP Server

Official

vs_alerts_list

Retrieve and filter organization alerts by status (unacknowledged, acknowledged, or resolved). Use pagination to navigate through results and manage alert workflows.

Instructions

List alerts for the authenticated organization. Filter by status (UNACKNOWLEDGED/ACKNOWLEDGED/RESOLVED) or paginate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoUNACKNOWLEDGED, ACKNOWLEDGED, or RESOLVED.
pageNo
limitNoDefault 50, max 200.

Implementation Reference

  • The handler function for vs_alerts_list. It makes a GET request to /api/alerts with optional query parameters (status, page, limit).
    handler: async (args, client) =>
      client.request('GET', '/api/alerts', {
        query: {
          status: pickString(args, 'status'),
          page: pickNumber(args, 'page'),
          limit: pickNumber(args, 'limit'),
        },
      }),
  • Input schema for vs_alerts_list: accepts optional status (string), page (integer), limit (integer) with additionalProperties disabled.
    inputSchema: {
      type: 'object',
      properties: {
        status: { ...STR, description: 'UNACKNOWLEDGED, ACKNOWLEDGED, or RESOLVED.' },
        page: { ...INT },
        limit: { ...INT, description: 'Default 50, max 200.' },
      },
      additionalProperties: false,
    },
  • src/tools.ts:324-346 (registration)
    Tool registration entry in the TOOLS array. The tool has name 'vs_alerts_list', requires authentication, and is wired to the handler.
    {
      name: 'vs_alerts_list',
      description:
        'List alerts for the authenticated organization. Filter by status (UNACKNOWLEDGED/ACKNOWLEDGED/RESOLVED) or paginate.',
      inputSchema: {
        type: 'object',
        properties: {
          status: { ...STR, description: 'UNACKNOWLEDGED, ACKNOWLEDGED, or RESOLVED.' },
          page: { ...INT },
          limit: { ...INT, description: 'Default 50, max 200.' },
        },
        additionalProperties: false,
      },
      requiresAuth: true,
      handler: async (args, client) =>
        client.request('GET', '/api/alerts', {
          query: {
            status: pickString(args, 'status'),
            page: pickNumber(args, 'page'),
            limit: pickNumber(args, 'limit'),
          },
        }),
    },
  • Helper function pickString used to safely extract the optional 'status' argument from the input args.
    function pickString(args: Record<string, unknown>, key: string): string | undefined {
      const v = args[key];
  • Helper function pickNumber used to safely extract optional numeric arguments 'page' and 'limit' from the input args.
    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?

No annotations provided, so the description carries the burden. It describes a read operation ('list alerts') but does not disclose other behavioral traits like rate limits, authentication requirements, or whether the result is paginated. Minimal but acceptable for a simple list tool.

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, no unnecessary words. Front-loaded with the primary action and parameters. Highly concise.

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

Completeness3/5

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

Given the tool's simplicity (3 parameters, no output schema, no annotations), the description provides enough context to understand basic usage. However, it omits details about return structure or ordering, which would be helpful for completeness.

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?

The description adds context for the status parameter (listing the enum values) and mentions pagination, which complements the schema's 67% coverage. However, it does not explain the 'page' parameter explicitly, leaving some ambiguity.

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 alerts for the authenticated organization, with specific filtering options (status values) and pagination. It distinguishes from sibling tools like vs_alerts_acknowledge.

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 when to use (to list alerts) but does not provide explicit guidance on when not to use it or how it compares to alternatives such as vs_alerts_acknowledge. No exclusions or context on prerequisites.

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