Skip to main content
Glama
Sign In
Code MCP Server

Code MCP Server

by agentics-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_workspace

Define the active workspace directory by providing an absolute path. This tool configures which directory the MCP server uses for file operations and code execution, enabling targeted interaction with a specific project folder.

Instructions

Set the active workspace directory

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

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to workspace directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility. It only states 'Set the active workspace directory' without any details on side effects, validation, persistence, or impact on other tools. This is insufficient for an agent to infer behavioral traits.

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?

The description is a single sentence with no wasted words. While it could beneficially include more context, it is appropriately sized for the tool's simplicity.

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

Completeness2/5

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

The description lacks critical context such as what happens if the path is invalid, whether the setting persists, or how it interacts with other workspace tools. For a state-changing tool, this is incomplete.

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?

The only parameter 'path' is fully described in the schema with 'Absolute path to workspace directory', so the description adds no extra meaning. Baseline score of 3 applies given 100% schema coverage.

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

Purpose4/5

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

The description clearly states the verb 'Set' and the resource 'active workspace directory', making the basic purpose evident. However, it does not differentiate from sibling tools like auto_select_workspace or present_workspace_choice, which also involve workspace selection.

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 alternatives. For example, it doesn't explain that this tool is for explicitly setting the path while other tools handle automatic selection or listing.

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