Skip to main content
Glama

get_workspace

Retrieve the absolute path of the current VS Code workspace to identify the active project directory.

Instructions

Get current workspace path

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function that executes the 'get_workspace' tool logic. It returns a ToolResult with the current workspace path.
    async getWorkspace(): Promise<ToolResult> {
      return {
        content: [{
          type: 'text',
          text: `Current workspace: ${this.workspacePath}`,
        }],
      };
    }
  • The tool definition/schema for 'get_workspace', including its name, description, and empty inputSchema (no parameters required).
    {
      name: 'get_workspace',
      description: 'Get current workspace path',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:130-133 (registration)
    The registration point where the 'get_workspace' tool name is matched in the executeToolCommand switch statement and delegated to workspaceService.getWorkspace().
    switch (name) {
      // Workspace Management
      case 'get_workspace':
        return await this.workspaceService.getWorkspace();
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only states it gets the path but does not mention error handling (e.g., if no workspace is set), return format, or side effects. This is minimal transparency.

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, concise sentence with no extraneous words. While it is appropriate for the tool's simplicity, it could benefit from slight expansion without losing conciseness.

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?

Given the tool's simplicity and lack of output schema or annotations, the description is incomplete. It does not clarify the return value format, error conditions, or when to use this tool among many siblings. More context is needed for effective decision-making.

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?

There are no parameters in the input schema, and schema description coverage is 100%. The description correctly implies no parameters are needed. With zero parameters, baseline is 4, as no additional parameter info is necessary.

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?

The description clearly states 'Get current workspace path', which is a specific verb and resource. It uniquely identifies the tool's purpose, distinguishing it from siblings like list_workspaces or set_workspace.

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 given on when to use this tool or when alternatives like list_workspaces or get_session_info might be more appropriate. The description lacks context about prerequisites or scenarios.

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/agentics-ai/code-mcp'

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