Skip to main content
Glama

cribl_restartWorkerGroup

Restart all workers in a worker group to apply configuration changes or recover from issues. Use this tool to trigger a coordinated restart of the specified worker group.

Instructions

Restarts all workers within the default or specified worker group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler that registers 'cribl_restartWorkerGroup' and calls the restartWorkerGroup client function, returning success/error responses.
    server.tool(
        'cribl_restartWorkerGroup',
        'Restarts all workers within the default or specified worker group.',
        RestartWorkerGroupArgsShape,
        async () => { // No args needed
            console.error(`[Tool Call] cribl_restartWorkerGroup`);
            const result = await restartWorkerGroup(); // Call client function without groupName
            if (!result.success) {
                console.error(`[Tool Error] cribl_restartWorkerGroup:`, result.error);
                return {
                    isError: true,
                    content: [{ type: 'text', text: `Error restarting workers: ${result.error}` }],
                };
            }
            console.error(`[Tool Success] cribl_restartWorkerGroup`);
            return {
                content: [{ type: 'text', text: result.data?.message || `Successfully initiated worker restart.` }],
            };
        }
    );
  • API helper function that calls PATCH /api/v1/master/workers/restart to restart all workers managed by the leader.
    export async function restartWorkerGroup(): Promise<ClientResult<{ message: string }>> { // Removed groupName parameter
        const context = `restartWorkerGroup`;
        // Using documented PATCH /master/workers/restart endpoint (No group scope)
        const url = `/api/v1/master/workers/restart`; 
        console.error(`[stderr] Attempting API call: PATCH ${url} - WARNING: This likely restarts ALL workers managed by the Leader.`);
        
        try {
            const response = await apiClient.patch(url); // Use PATCH, no body usually needed for restart action
            return { success: true, data: { message: `Successfully initiated worker restart. Response status: ${response.status}` } };
        } catch (error) {
            const errorMessage = handleApiError(error, context);
            return { success: false, error: errorMessage };
        }
    }
  • src/server.ts:311-312 (registration)
    Registration of the 'cribl_restartWorkerGroup' tool via server.tool() on the MCP server instance.
    server.tool(
        'cribl_restartWorkerGroup',
  • Empty schema definition for restartWorkerGroup tool since no arguments are required.
    const RestartWorkerGroupArgsShape = {}; // No args needed
Behavior2/5

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

No annotations are provided, and the description fails to disclose behavioral traits such as whether a restart disrupts ongoing operations, requires authentication, or is reversible. 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.

Conciseness5/5

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

The description is a single, clear sentence of 10 words, efficiently stating the tool's purpose with no redundancy.

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?

For a tool with no annotations or output schema, the description should provide more context. It fails to explain how to specify a worker group (conflicting with the schema), what the default group is, or what occurs after restarting. Incomplete.

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?

With zero parameters in the input schema, the description does not need to add parameter details. The baseline for 0 parameters is 4, and the description does not contradict that (though it implies a parameter for worker group selection).

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 ('restarts') and the resource ('all workers within the default or specified worker group'), distinguishing it from sibling tools that focus on pipelines, sources, or metrics.

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 mentions a 'specified worker group' but the input schema has no parameters to select one, creating ambiguity. No guidance is given on when to use this tool versus alternatives like cribl_listWorkerGroups or other restart mechanisms.

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/pebbletek/cribl-mcp'

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