Laravel Forge MCP Server (Extended)

delete_worker

Delete a specific queue worker from a site on a server. Provide server, site, and worker IDs to remove it.

Instructions

Delete 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": "delete_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

B3.2/5.0

Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It only states 'delete' without disclosing if operation is irreversible, requires permissions, or triggers immediate side effects. Minimal transparency.

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?

Single sentence, no wasted words. Front-loaded with action and resource. Slightly brief but effective for a simple delete operation.

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?

For a simple delete with no output schema and only required IDs, the description is minimally complete. However, it could mention confirmation behavior or safety considerations.

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 covers all 3 parameters with descriptions (IDs). Description adds no extra meaning beyond schema. Baseline score of 3 is appropriate given 100% schema coverage.

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 (delete) and resource (queue worker). It distinguishes from siblings like create_worker, restart_worker, and list_workers, which involve different operations.

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 (e.g., restart_worker), prerequisites (e.g., worker must be stopped), or consequences (e.g., irreversible). Users are left to infer context.

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