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

dev-env-mcp

by Tova501
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

env_create

Create a Python virtual environment in your project workspace and activate it for isolated dependency management.

Instructions

Create a venv inside the active workspace (default: .venv) and set it active.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "env_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.venv

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description bears full responsibility. It states that the venv is created and set active, but omits details like whether an existing .venv is overwritten, required permissions, or side effects on the environment.

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 sentence that efficiently conveys the purpose, default, and activation behavior with no redundant or extraneous content.

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?

For a simple tool with one optional parameter and an output schema, the description covers the core functionality. However, it does not mention potential prerequisites (e.g., workspace existence) or failure modes, leaving some gap.

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 schema has one parameter 'path' with a default but no description. The description explains the parameter's purpose and default, adding meaning beyond the schema. It indicates the venv is created at the specified path, defaulting to '.venv'.

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 action ('create'), the resource ('venv'), and the context ('inside the active workspace'). It specifies the default path and notes that it sets the env active, distinguishing it from sibling tools like env_use and pip.

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

Usage Guidelines3/5

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

The description implies when to use (when a new venv is needed in the workspace) but does not explicitly state when not to use or provide alternatives. Sibling env_use suggests an alternative, but no guidance is given.

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