Skip to main content
Glama

List Workspaces

list_workspaces
Read-only

Lists active workspaces and pool limits so you can see which slots are occupied before claiming or closing one.

Instructions

List the live workspaces (freecadcmd processes) and the pool limits. Each entry is {name, alive, idle_s, current}. Use to see who is holding a slot before claiming or closing one.

current is the workspace THIS call runs in: the workspace you passed, else the use_workspace selection. selected is that server-wide selection, which a pinned call neither follows nor moves. Returns {current, selected, max, idle_reap_s, workspaces: [...]}.

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": "list_workspaces"
  }
}

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
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds the real behavioral payload — that entries are live process snapshots with an idle timestamp, and how `current` relates to the pinned `workspace` argument versus the server-wide `selected`. It does not discuss cost or whether a listing can force-reap stale workers, but for a read-only lister the essential traits are covered.

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 purpose and entry shape, then the current/selected semantics, then the return object — a sensible ordering. It is dense with backticked identifiers and the current/selected distinction takes two sentences to land, but no sentence is filler.

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?

There is no output schema, so the description takes on the return contract itself and does so precisely ({current, selected, max, idle_reap_s, workspaces: [...]}), matching it to the entry field list. For a zero-required-parameter read tool, an agent has everything needed to call and interpret it.

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?

Coverage is 100%, so the schema already documents `workspace`, yet the description adds the precedence rule a caller could not infer: the passed workspace wins, otherwise the use_workspace selection applies, and a pinned call neither follows nor moves `selected`. That is genuine semantic value beyond the one-line schema text.

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 and resource ('List the live workspaces (freecadcmd processes)') and extends it to pool limits, then gives the entry shape {name, alive, idle_s, current}. Defining a workspace as a freecadcmd process disambiguates it from documents, sketches, and other objects in a very crowded sibling list.

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?

'Use to see who is holding a slot before claiming or closing one' gives a clear trigger that implicitly points at use_workspace and close_workspace. It stops short of naming those siblings explicitly or stating when not to call this (e.g., that it is diagnostic-only and does not change allocation).

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