Skip to main content
Glama
Sign In
dev-env-mcp

dev-env-mcp

by Tova501
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

workspace_use

Select a project workspace to manage Python environments. Automatically detects the workspace root and restricts all future operations to that workspace.

Instructions

Select the project/workspace to manage.

  • 'path' can be a repo root or any subdirectory inside a repo.

  • The server will auto-find the workspace root by walking up to pyproject.toml or .git.

  • All future operations (env_create/pip/freeze) are sandboxed to this workspace.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description effectively discloses behaviors: path can be any subdirectory, server auto-finds root, and sandboxes future operations. This adds value beyond basic read/write hints.

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 concise with bullet points, each sentence adding value. It is front-loaded with the main purpose and structured for quick parsing.

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

Completeness4/5

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

Given the single parameter, existing output schema, and sibling tools, the description provides sufficient context for workspace selection. It could mention return values but is still adequate.

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?

The 'path' parameter has no schema description (0% coverage), but the tool description compensates by explaining acceptable values (repo root or subdirectory) and auto-resolution behavior.

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 the tool selects the project/workspace to manage. It distinguishes from siblings like env_create, env_use, freeze, and pip by focusing on 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 Guidelines4/5

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

The description explains that future operations are sandboxed to this workspace, implying it should be used before other tools. It provides context but lacks explicit when-not-to-use.

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