Skip to main content
Glama
bazinga012

MCP Code Executor

get_environment_config

Retrieve the current environment configuration to verify available Python libraries and dependencies for code execution.

Instructions

Get the current environment configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'get_environment_config' tool, which returns the current environment configuration (ENV_CONFIG) as a JSON string in the response content.
    case "get_environment_config": {
        return {
            content: [{
                type: "text",
                text: JSON.stringify({
                    status: 'success',
                    config: ENV_CONFIG
                }),
                isError: false
            }]
        };
    }
  • The tool schema definition including name, description, and empty input schema (no parameters required). This is part of the tools list returned by listTools.
    {
        name: "get_environment_config",
        description: "Get the current environment configuration",
        inputSchema: {
            type: "object",
            properties: {}
        }
    }
  • src/index.ts:678-687 (registration)
    Registration of the tool in the listTools response handler, defining it as available with its schema.
            {
                name: "get_environment_config",
                description: "Get the current environment configuration",
                inputSchema: {
                    type: "object",
                    properties: {}
                }
            }
        ]
    };
  • Global ENV_CONFIG object used by the get_environment_config handler, initialized from environment variables.
    let ENV_CONFIG: EnvironmentConfig = {
        // Default environment (conda, venv, or venv-uv)
        type: (process.env.ENV_TYPE || 'conda') as 'conda' | 'venv' | 'venv-uv',
        // Name of the conda environment
        conda_name: process.env.CONDA_ENV_NAME,
        // Path to virtualenv
        venv_path: process.env.VENV_PATH,
        // Path to uv virtualenv
        uv_venv_path: process.env.UV_VENV_PATH
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get' implies a read operation, but doesn't specify what 'environment configuration' includes (e.g., variables, paths, dependencies), whether it requires permissions, if it's cached or real-time, or what happens on errors. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior beyond the basic action.

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, clear sentence: 'Get the current environment configuration.' It's front-loaded with the core action and resource, with no wasted words or redundant information. This is appropriately sized and efficient for a simple tool.

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

Completeness3/5

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

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on output format, error handling, or how it differs from siblings. Without annotations or output schema, more context on return values or behavioral traits would improve completeness, but it's not entirely incomplete for such a simple tool.

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 input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't add parameter details, which is appropriate since there are none to explain. This meets the baseline of 4 for tools with zero parameters, as there's no need to compensate for missing schema information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get the current environment configuration' clearly states the verb ('Get') and resource ('environment configuration'), making the purpose understandable. However, it doesn't distinguish this tool from potential sibling tools like 'configure_environment' or 'check_installed_packages' that might also interact with environment settings, leaving some ambiguity about its specific scope.

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. With siblings like 'configure_environment' (which might modify settings) and 'check_installed_packages' (which might list installed components), there's no indication of whether this tool is for read-only access, current runtime settings, or other specific contexts. It lacks explicit when/when-not instructions or named alternatives.

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/bazinga012/mcp_code_executor'

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