Skip to main content
Glama

local_dev_from_filesystem

Create a local development environment from a filesystem path to run tests and view coverage in sandboxed Python, Node, or Bun projects.

Instructions

Create a new local development environment from a filesystem path

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesLocal filesystem path

Implementation Reference

  • Handler for the local_dev_from_filesystem tool: calls create_environment_from_path and formats response with environment details.
    elif name == "local_dev_from_filesystem":
        env = await create_environment_from_path(arguments["path"])
        return [
            types.TextContent(
                type="text",
                text=json.dumps(
                    {
                        "success": True,
                        "data": {
                            "id": env.id,
                            "working_dir": str(env.sandbox.work_dir),
                            "created_at": env.created_at.isoformat(),
                            "runtime": env.runtime_config.name.value,
                        },
                    }
                ),
            )
        ]
  • Input schema and metadata for the local_dev_from_filesystem tool, registered in the tools list.
    types.Tool(
        name="local_dev_from_filesystem",
        description="Create a new local development environment from a filesystem path",
        inputSchema={
            "type": "object",
            "properties": {
                "path": {"type": "string", "description": "Local filesystem path"}
            },
            "required": ["path"],
        },
    ),
  • Main helper function implementing the environment creation from a local path: sandbox creation, file copy, runtime detection and installation.
    async def create_environment_from_path(path: Path) -> Environment:
        """Create new environment from filesystem path."""
        env_id = b58_fuuid()
        sandbox = await create_sandbox(f"mcp-{env_id}-")
    
        shutil.copytree(path, sandbox.work_dir, dirs_exist_ok=True)
        os.chmod(sandbox.work_dir, 0o700)
        os.chmod(sandbox.bin_dir, 0o700)
    
        runtime_config = detect_runtime(sandbox)
        await install_runtime(sandbox, runtime_config)
    
        env = Environment(
            id=env_id,
            runtime_config=runtime_config,
            sandbox=sandbox,
            created_at=datetime.now(timezone.utc),
        )
    
        _ENVIRONMENTS[env_id] = env
        return env
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool creates something but doesn't specify what 'local development environment' entails, whether it requires specific permissions, if it's destructive to existing environments, or what happens on failure. This leaves significant gaps for a creation tool.

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 a single, efficient sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized for a tool with one parameter and gets straight to the point without unnecessary elaboration.

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?

For a creation tool with no annotations, no output schema, and siblings that suggest complex operations (cleanup, tests), the description is insufficient. It doesn't explain what constitutes a 'local development environment', what gets created, or what the expected outcome is. The agent lacks crucial context to use this tool effectively.

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 schema description coverage is 100%, with the single parameter 'path' documented as 'Local filesystem path'. The description adds no additional parameter information beyond what's in the schema. According to guidelines, when schema coverage is high (>80%), the baseline is 3 even with no param info in description.

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 action ('Create a new local development environment') and the resource ('from a filesystem path'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'local_dev_from_github' which serves a similar purpose but from a different source.

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?

The description provides no guidance on when to use this tool versus alternatives like 'local_dev_from_github' or 'local_dev_cleanup'. It lacks any context about prerequisites, when this approach is preferred, or what happens if the path is invalid. The agent must infer usage from the tool name alone.

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/txbm/mcp-local-dev'

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