Lab Virtual MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your private API key | |
| Baseurl | Yes | Your seed phrase or base URL | |
| compnaykey | Yes | Your company private key | |
| PROJECT_PATH | Yes | The path to the project directory where app.py is located |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_codeC | Execute code in a secure sandbox environment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'execute_code' has a clear, distinct purpose that cannot be confused with any other tool in the set.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'execute_code' follows a clear verb_noun pattern, which would be consistent if more tools were added.
One tool is generally too few for a server's purpose, as it limits functionality and may not cover the domain adequately. For a 'Lab Virtual MCP Server' that likely involves code execution, additional tools for managing environments, listing sessions, or handling inputs/outputs would be expected.
The tool set is severely incomplete for the inferred domain of a lab or virtual environment. With only an 'execute_code' tool, there are obvious gaps such as creating or deleting environments, listing available sessions, handling file uploads/downloads, or monitoring execution status, which are essential for a coherent workflow.