Skip to main content
Glama
Sign In
patchwork-os

patchwork-os

by Oolab-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

setActiveWorkspaceFolder

Idempotent

Sets the active workspace folder for file operations. Use to switch focus in multi-root workspaces.

Instructions

Set active workspace folder for file ops. Useful in multi-root workspaces.

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

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to the workspace folder to activate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide idempotentHint: true, indicating safe repeated calls. The description adds minimal context (file ops, multi-root) but does not elaborate on side effects, permissions, or behavior beyond the annotation. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences, front-loaded with the core action and purpose. Every word is informative with no redundancy. Ideal length for a simple tool.

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

Completeness4/5

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

For a simple tool with one required parameter, no output schema, and clear annotations, the description provides sufficient context to understand when and how to use it. Could hint at prerequisites (e.g., workspace must be multi-root) but overall adequate.

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?

Input schema covers the single parameter 'path' with a clear description matching the tool's purpose. With 100% schema coverage, the description adds no further parameter details, so baseline score of 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?

Description clearly states the action 'Set active workspace folder' and its purpose 'for file ops', with specific context 'Useful in multi-root workspaces'. This distinguishes it from sibling tools like getWorkspaceFolders (read-only) and setWorkspaceSetting (general setting).

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

Usage Guidelines3/5

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

The description implies usage in multi-root workspaces but does not provide explicit guidance on when to use vs. alternatives (e.g., when to choose this over getWorkspaceFolders or other folder-related tools). No exclusion scenarios are given.

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