Skip to main content
Glama

Use Workspace

use_workspace

Claims or creates an isolated workspace and targets later tool calls to it, keeping FreeCAD documents and handles separate. Use unique workspaces for concurrent agents.

Instructions

Claim (creating if needed) an isolated workspace and make it the target of subsequent tool calls. Each workspace is its own freecadcmd process with its own ActiveDocument and handle registry — handles do NOT cross workspaces.

The selection is SERVER-WIDE: it retargets every client sharing this server, including other subagents of the same session. Concurrent agents must instead pass workspace=<unique name> on every tool call, which pins just that call and leaves this selection alone.

The pool is capped (ANKUSDRIVE_MAX_WORKSPACES, default 4) and idle workspaces are reaped (ANKUSDRIVE_WORKSPACE_IDLE_S, default 900s); claiming a workspace beyond a full pool raises — close an idle one first. Pass "default" to return to the baseline single-agent workspace. Returns {workspace: , freecad: [...], workspaces: [names]}.

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": {
      "name": "<name>"
    },
    "name": "use_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
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.6/5.0
Behavior5/5

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

Goes far beyond annotations (readOnlyHint=false, destructiveHint=false): it discloses that the selection is SERVER-WIDE and retargets every client including sibling subagents, that each workspace is a separate freecadcmd process with its own handle registry so handles do not cross boundaries, the pool cap (ANKUSDRIVE_MAX_WORKSPACES, default 4), idle reaping (default 900s), and that over-claiming raises.

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 core action and scope, then progressively discloses the multitenancy caveat, pool limits, and return shape. Dense but nearly every sentence carries operational information; the parenthetical env-var defaults add slight bulk without hurting usability.

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?

Given no output schema, the description supplies the return shape ({workspace, freecad, workspaces}), the failure mode on a full pool, and the lifecycle rules for idle reaping. For a stateful, server-wide mutation this covers everything an agent needs before invoking it.

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 50%: `workspace` is documented in the schema while `name` is not. The description compensates for `name` by explaining claim-or-create semantics and the special "default" value, but it never states whether `name` accepts arbitrary strings, how names are normalized, or how `workspace` interacts with the selection when passed on this tool itself. Adequate but not fully clarifying.

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?

Opens with a specific verb+resource: 'Claim (creating if needed) an isolated workspace and make it the target of subsequent tool calls.' It immediately establishes this as a selection/configuration operation, distinct from siblings like list_workspaces and close_workspace.

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

Usage Guidelines5/5

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

Explicitly states the alternative path: concurrent agents 'must instead pass workspace=<unique name> on every tool call, which pins just that call and leaves this selection alone.' It also gives the reset case ('Pass "default" to return to the baseline') and the precondition that a full pool raises, so close an idle one first.

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