Skip to main content
Glama
VisualSentinel

Visual Sentinel MCP Server

Official

vs_servers_list

Retrieve a paginated list of servers registered in the authenticated organization.

Instructions

List servers (origins) registered in the authenticated organization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
limitNoDefault 50.

Implementation Reference

  • src/tools.ts:379-395 (registration)
    Tool definition registration: vs_servers_list is defined as a ToolDefinition object in the TOOLS array with name, description, inputSchema, requiresAuth, and handler.
    {
      name: 'vs_servers_list',
      description: 'List servers (origins) registered in the authenticated organization.',
      inputSchema: {
        type: 'object',
        properties: {
          page: { ...INT },
          limit: { ...INT, description: 'Default 50.' },
        },
        additionalProperties: false,
      },
      requiresAuth: true,
      handler: async (args, client) =>
        client.request('GET', '/api/servers', {
          query: { page: pickNumber(args, 'page'), limit: pickNumber(args, 'limit') },
        }),
    },
  • Input schema for vs_servers_list: accepts optional 'page' (integer) and 'limit' (integer, default 50) properties.
    inputSchema: {
      type: 'object',
      properties: {
        page: { ...INT },
        limit: { ...INT, description: 'Default 50.' },
      },
      additionalProperties: false,
    },
  • Handler function: calls client.request('GET', '/api/servers') with query params page and limit extracted via pickNumber helper.
    handler: async (args, client) =>
      client.request('GET', '/api/servers', {
        query: { page: pickNumber(args, 'page'), limit: pickNumber(args, 'limit') },
      }),
  • pickNumber helper: extracts a finite number from args, used to parse page/limit for the handler.
    function pickNumber(args: Record<string, unknown>, key: string): number | undefined {
      const v = args[key];
      return typeof v === 'number' && Number.isFinite(v) ? v : undefined;
    }
  • src/index.ts:45-46 (registration)
    MCP SDK registration: the CallToolRequestSchema handler looks up tools by name via findTool (which searches TOOLS array) and invokes the handler.
    server.setRequestHandler(CallToolRequestSchema, async (req) => {
      const tool = findTool(req.params.name);
Behavior2/5

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

With no annotations provided, the description carries all burden for behavioral disclosure. It lacks details on pagination behavior, rate limits, ordering, or any side effects, making it insufficient for a clear understanding of the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no wasted words. However, it is arguably too short for a list operation that could benefit from more detail.

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 low complexity (2 simple parameters, no output schema), the description is somewhat complete but lacks pagination details or filtering options. It is minimal but adequate for a basic list tool.

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

Parameters2/5

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

Schema coverage is 50%: only 'limit' has a description ('Default 50'), while 'page' has no description. The tool description adds no additional meaning beyond the schema, failing to compensate for the missing parameter documentation.

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 'List servers' and specifies the resource 'servers (origins)' and scope 'in the authenticated organization'. This distinguishes it from sibling list tools like vs_alerts_list and vs_monitors_list.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no context on pagination or filtering. It only states the action without usage instructions.

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