Skip to main content
Glama
skippr-hq

Skippr Extension MCP Server

by skippr-hq

Extension Server Status

skippr_extension_server_status

Checks the WebSocket server status for browser extensions to ensure connectivity for issue detection and resolution.

Instructions

Gets the current status of the WebSocket server for browser extensions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
runningYes
portNo

Implementation Reference

  • Registers the 'skippr_extension_server_status' tool with MCP server, defining input/output schemas and wiring to the handler function.
    mcpServer.registerTool(
      'skippr_extension_server_status',
      {
        title: 'Extension Server Status',
        description: 'Gets the current status of the WebSocket server for browser extensions',
        inputSchema: {},
        outputSchema: z.object({
          running: z.boolean(),
          port: z.number().optional()
        }).shape
      },
      async () => {
        const result = getWebSocketServerStatus();
        return createStructuredResponse(result);
      }
    );
  • The async handler function for 'skippr_extension_server_status' that calls getWebSocketServerStatus() and returns a structured response.
      async () => {
        const result = getWebSocketServerStatus();
        return createStructuredResponse(result);
      }
    );
  • The getWebSocketServerStatus() function that returns the current status (running, port) of the WebSocket server by checking the global wss instance.
    export function getWebSocketServerStatus(): { running: boolean; port?: number } {
      if (wss) {
        const address = wss.address();
        if (address && typeof address === 'object') {
          return { running: true, port: address.port };
        }
        return { running: true };
      }
      return { running: false };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose what the status object contains (e.g., connection state, latency) or any potential side effects (e.g., network call). The description is minimal.

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, clear sentence that is front-loaded with the key action. However, it could be slightly more informative without losing conciseness, e.g., mentioning the output format.

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 has no parameters and an output schema exists, the description is adequate but not fully complete. It does not clarify what 'status' means (e.g., 'connected' vs 'disconnected'), which a user might need to interpret the output.

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

Parameters4/5

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

The tool has zero parameters, and the schema coverage is 100%. The description adds no parameter details because none exist, but it correctly implies no inputs are needed. Baseline for 0 params is 4.

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 it 'gets the current status of the WebSocket server for browser extensions,' with a specific verb and resource. It distinguishes itself from sibling tools like 'restart' or 'disconnect' which modify state.

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?

No guidance on when to use this tool versus alternatives such as 'restart_extension_server' or 'list_connected_extensions'. The description does not provide any context about prerequisites or typical use cases.

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/skippr-hq/extension-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server