Feature summary (what you would like to be able to do and where):
Have a new environment available for all tools on Toolforge, giving the name of the tool you're in.
Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
I have a tool with an oauth process using non-confidential credentials (hence why they are not in env variables themselves). There are (or will be) two versions of the app on two separate tools, one beta and the other one main. The oauth process involves a callback URL. The domain name in the address is decided by the tool's name, so I need the tool's name to know which configuration and set of credentials to use as part of the build process of my tool.
Benefits (why should this be implemented?):
There is a TOOL_DATA_DIR that provides a path specific to the tool, seemingly ending with the tool's name as last component, provided for all tools on Toolforge.
It would be a good idea to have the tool's name directly accessible, for instance through a TOOL_NAME variable.