Skip to main content
Glama

Restart Worker

restart_worker
Destructive

Kill the current workspace's wedged FreeCAD worker and spawn a fresh process to recover from a desynced or stuck state. Save first; unsaved changes in that workspace are lost.

Instructions

Kill the current workspace's FreeCAD worker process and spawn a fresh one. Use when the worker is wedged (e.g. App.ActiveDocument desynced from internal state). All open documents, unsaved changes, and handles in THIS workspace are lost — save first if needed. Other workspaces are untouched. Returns {restarted: True, workspace: , freecad: [...]}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "restart_worker"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's job is to add specifics — and it does: exactly what is destroyed (open documents, unsaved changes, handles), scoped to this workspace only, plus the return payload shape. That is precisely the added context annotations cannot carry.

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?

Front-loaded with the action, then trigger, then risk, then return value — a sensible ordering with no filler. It is four sentences where three might do, but every sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by spelling out the return shape. Combined with the trigger condition, data-loss warning, and workspace scoping, an agent has everything needed to decide and call correctly for this destructive one-param tool.

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% and the single optional 'workspace' param is documented there with a default of ''. The description reinforces the notion of operating on 'THIS workspace' but never explains what happens when the workspace argument is supplied versus left empty, so it adds only marginal meaning over the schema. Baseline 3 applies.

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?

States a specific verb pair ('kill ... and spawn') on a specific resource ('the current workspace's FreeCAD worker process'), with explicit scope. An agent can distinguish this from siblings like close_workspace, ping, or setup_status without opening any schema.

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

Usage Guidelines4/5

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

Gives a concrete trigger condition ('when the worker is wedged, e.g. App.ActiveDocument desynced from internal state') plus a prerequisite ('save first if needed') and a blast-radius exclusion ('other workspaces are untouched'). It stops short of naming a named alternative tool (e.g. close_workspace / use_workspace) for the non-wedged case.

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

Deploy Server

Other Tools