Laravel Forge MCP Server (Extended)

restart_worker

Restart a queue worker on a Laravel Forge site to resolve stalled or unresponsive queues and maintain continuous background job processing.

Instructions

Restart a queue worker

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serverId": "<serverId>",
      "siteId": "<siteId>",
      "workerId": "<workerId>"
    },
    "name": "restart_worker"
  }
}

Input Schema

Name	Required	Description
`siteId`	Yes	The ID of the site
`serverId`	Yes	The ID of the server
`workerId`	Yes	The ID of the worker

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jul 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Restart', which implies stopping and starting, but does not mention whether it is graceful, if queued jobs are affected, or any side effects. Additional context is needed.

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 sentence with no wasted words. It is concise but could benefit from a bit more structure or context without becoming verbose.

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 simple nature of restarting a worker and full schema coverage, the description is minimally adequate. However, it lacks information about return values or post-restart behavior, which is not compensated by an output schema.

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 100%, so baseline is 3. The description adds no extra meaning beyond the schema; it merely repeats the action. No parameter details or format hints are provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Restart' and the resource 'a queue worker', which is distinct from sibling tools like create_worker or delete_worker. However, it does not explicitly differentiate from restart_daemon, so clarity could be improved.

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 is provided on when to use this tool versus alternatives such as restart_daemon or create_worker. There is no mention of prerequisites, context, or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.