Skip to main content
Glama
devlimelabs

MCP Environment & Installation Manager

by devlimelabs

list-env-vars

Display environment variables for a specific profile to manage configurations in the MCP Environment & Installation Manager.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileIdYesProfile ID to list environment variables from

Implementation Reference

  • Registration of the 'list-env-vars' MCP tool, including the input schema (profileId parameter) and the complete inline handler function that lists environment variables for a profile, masking sensitive ones.
    // List environment variables
    server.tool(
      "list-env-vars",
      {
        profileId: z.string().describe("Profile ID to list environment variables from")
      },
      async ({ profileId }, extra) => {
        if (!profileId.trim()) {
          throw new Error("Profile ID cannot be empty");
        }
        
        const profile = configService.getProfile(profileId);
        if (!profile) {
          throw new Error(`Profile not found: ${profileId}`);
        }
        
        const envVars = configService.getEnvVars(profileId);
        
        // Transform to array and mask sensitive values
        const result = Object.entries(envVars).map(([key, envVar]) => ({
          key,
          value: envVar.sensitive ? '********' : envVar.value,
          sensitive: envVar.sensitive,
          description: envVar.description
        }));
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                profileId,
                profileName: profile.name,
                variables: result
              }, null, 2)
            }
          ]
        };
      }
    );
  • The handler function implementing the core logic of 'list-env-vars': validates profileId, retrieves profile and env vars via ConfigService, formats output masking sensitive values, and returns structured text content.
    async ({ profileId }, extra) => {
      if (!profileId.trim()) {
        throw new Error("Profile ID cannot be empty");
      }
      
      const profile = configService.getProfile(profileId);
      if (!profile) {
        throw new Error(`Profile not found: ${profileId}`);
      }
      
      const envVars = configService.getEnvVars(profileId);
      
      // Transform to array and mask sensitive values
      const result = Object.entries(envVars).map(([key, envVar]) => ({
        key,
        value: envVar.sensitive ? '********' : envVar.value,
        sensitive: envVar.sensitive,
        description: envVar.description
      }));
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              profileId,
              profileName: profile.name,
              variables: result
            }, null, 2)
          }
        ]
      };
    }
  • Input schema for 'list-env-vars' tool defining the required 'profileId' parameter using Zod.
    {
      profileId: z.string().describe("Profile ID to list environment variables from")
    },
  • src/server.ts:31-31 (registration)
    High-level registration call that invokes registerEnvironmentTools, thereby registering 'list-env-vars' and other environment tools on the MCP server.
    registerEnvironmentTools(server, configService);
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/devlimelabs/mcp-env-manager-mcp'

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