Skip to main content
Glama
FutureAtoms

Agentic Control Framework (ACF)

by FutureAtoms

setWorkspace

Set the active workspace directory to define the context for file and terminal operations.

Instructions

Set workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspacePathYes

Implementation Reference

  • The handler logic for the setWorkspace tool. It checks if the provided workspacePath exists on disk, then updates the workspaceRoot variable and allowedDirectories[0] to the new path.
    case 'setWorkspace':
      if (args.workspacePath && fs.existsSync(args.workspacePath)) {
        workspaceRoot = args.workspacePath;
        allowedDirectories[0] = workspaceRoot;
        logger.info(`Workspace root set to: ${workspaceRoot}`);
        data = { success: true, message: `Workspace set to ${workspaceRoot}` };
      } else { data = { success:false, message:`Invalid or non-existent workspace path: ${args.workspacePath}` }; }
      break;
  • The tool registration schema for setWorkspace, defining its inputSchema with a required workspacePath string parameter.
    { name:'setWorkspace', description:'Set workspace', inputSchema:{ type:'object', properties:{ workspacePath:{ type:'string' } }, required:['workspacePath'] } },
  • The tool is registered as part of the tools/list handler's tools array in src/mcp/server.js.
    { name:'setWorkspace', description:'Set workspace', inputSchema:{ type:'object', properties:{ workspacePath:{ type:'string' } }, required:['workspacePath'] } },
  • A test/usage example of setWorkspace in the MCP scenario runner script.
    console.log('[MCP] setWorkspace');
    console.log(unwrapCall(await req('tools/call', { name: 'setWorkspace', arguments: { workspacePath: WORKSPACE } })));
  • Usage of setWorkspace in the SWE-bench integration test script.
    workspace_result = await acf_client.call_tool("setWorkspace", {
        "workspacePath": f"/tmp/swebench_test/{instance_id}"
    })
Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits such as side effects, permissions needed, or what changes occur when setting the workspace. The agent has no insight into the tool's impact.

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

Conciseness2/5

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

At two words, the description is extremely short, but this is under-specification rather than conciseness. It fails to convey essential information, so brevity is detrimental.

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

Completeness1/5

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

Given the lack of annotations, output schema, and parameter descriptions, the description is completely inadequate. The tool may perform a critical function, but the description provides no actionable context for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage for the parameter 'workspacePath'. The description adds no meaning beyond the schema, not even explaining what 'workspacePath' represents (e.g., file path, directory, URL).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Set workspace' is a verb+resource but lacks specificity. It does not clarify what a 'workspace' refers to (e.g., directory, configuration context), making the tool's purpose vague and ambiguous.

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 is provided on when to use this tool versus siblings. The description offers no context, preconditions, or alternatives, leaving the agent without decision-making information.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FutureAtoms/agentic-control-framework'

If you have feedback or need assistance with the MCP directory API, please join our Discord server