Skip to main content
Glama

workspace_unmount

Unmount a virtual filesystem workspace to release resources and disconnect from storage providers.

Instructions

Unmount workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo

Implementation Reference

  • Core handler function that executes the unmount logic: checks mount status, updates workspace info (sets is_mounted=False), and returns response. Note: FUSE unmount is TODO.
    async def workspace_unmount(
        self, name: str | None = None
    ) -> WorkspaceUnmountResponse:
        """
        Unmount workspace.
    
        Args:
            name: Workspace name (None for current)
    
        Returns:
            WorkspaceUnmountResponse with success status
        """
        info = self.workspace_manager.get_workspace_info(name)
    
        if not info.is_mounted:
            return WorkspaceUnmountResponse(
                success=False,
                workspace=info.name,
                error=f"Workspace '{info.name}' is not mounted",
            )
    
        # TODO: Implement FUSE unmounting
        info.is_mounted = False
        mount_point = info.mount_point
        info.mount_point = None
    
        return WorkspaceUnmountResponse(
            success=True, workspace=info.name, mount_point=mount_point
        )
  • MCP tool registration using @server.tool decorator. This is the entry point handler that delegates to the underlying workspace_tools implementation.
    @server.tool
    async def workspace_unmount(name: str | None = None):
        """Unmount workspace."""
        return await workspace_tools.workspace_unmount(name)
  • Pydantic BaseModel defining the output schema for the workspace_unmount tool response.
    class WorkspaceUnmountResponse(BaseModel):
        """Response from workspace unmount"""
    
        success: bool
        workspace: str
        mount_point: str | None = None
        error: str | None = None
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. 'Unmount workspace' implies a mutation operation that likely changes state, but it does not explain what unmounting does (e.g., disconnecting a workspace from a filesystem, freeing resources), whether it's reversible, what permissions are required, or any side effects. This lack of detail makes it inadequate for a tool with potential destructive implications.

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?

The description is extremely concise with just two words, 'Unmount workspace,' which is front-loaded and wastes no space. While this brevity contributes to under-specification, it scores highly on conciseness as every word serves a purpose, albeit insufficiently.

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 complexity of a workspace operation with no annotations, no output schema, and a parameter with 0% schema coverage, the description is severely incomplete. It does not explain the tool's purpose, usage, behavior, or parameters adequately, failing to provide the necessary context for an AI agent to use it correctly.

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

Parameters2/5

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

The input schema has one parameter ('name') with 0% description coverage, so the description must compensate. However, the description adds no information about parameters—it does not mention 'name' or explain what it represents (e.g., workspace identifier). This leaves the parameter undocumented and fails to bridge the coverage gap.

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 'Unmount workspace' is essentially a tautology that restates the tool name 'workspace_unmount' without adding meaningful context. It specifies the verb ('unmount') and resource ('workspace'), but lacks any detail about what unmounting entails or how it differs from sibling tools like 'workspace_destroy' or 'workspace_switch', making it vague and minimally informative.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. There are multiple sibling tools related to workspaces (e.g., 'workspace_destroy', 'workspace_switch', 'workspace_mount'), but the description fails to specify scenarios for unmounting, prerequisites, or exclusions, leaving the agent with no usage context.

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/IBM/chuk-mcp-vfs'

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