Skip to main content
Glama
devlimelabs

MCP Environment & Installation Manager

by devlimelabs

get-env-var

Retrieve environment variable values from specific profiles in the MCP Environment & Installation Manager for configuration management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileIdYesProfile ID to get environment variable from
keyYesEnvironment variable key

Implementation Reference

  • Handler function that implements the logic for the 'get-env-var' tool: validates profileId and key, retrieves the profile and environment variable using ConfigService, handles errors, masks sensitive values, and returns a structured text response.
    async ({ profileId, key }, extra) => {
      if (!profileId.trim()) {
        throw new Error("Profile ID cannot be empty");
      }
      
      if (!key.trim()) {
        throw new Error("Environment variable key cannot be empty");
      }
      
      const profile = configService.getProfile(profileId);
      if (!profile) {
        throw new Error(`Profile not found: ${profileId}`);
      }
      
      const envVar = configService.getEnvVar(profileId, key);
      if (!envVar) {
        throw new Error(`Environment variable not found: ${key}`);
      }
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              profileId,
              profileName: profile.name,
              key,
              value: envVar.sensitive ? '********' : envVar.value,
              sensitive: envVar.sensitive,
              description: envVar.description
            }, null, 2)
          }
        ]
      };
    }
  • Zod input schema for the 'get-env-var' tool, defining required parameters profileId (string) and key (string) with descriptions.
    {
      profileId: z.string().describe("Profile ID to get environment variable from"),
      key: z.string().describe("Environment variable key")
    },
  • Direct registration of the 'get-env-var' tool using server.tool(), specifying the tool name, input schema, and handler function within the registerEnvironmentTools function.
    server.tool(
      "get-env-var",
      {
        profileId: z.string().describe("Profile ID to get environment variable from"),
        key: z.string().describe("Environment variable key")
      },
      async ({ profileId, key }, extra) => {
        if (!profileId.trim()) {
          throw new Error("Profile ID cannot be empty");
        }
        
        if (!key.trim()) {
          throw new Error("Environment variable key cannot be empty");
        }
        
        const profile = configService.getProfile(profileId);
        if (!profile) {
          throw new Error(`Profile not found: ${profileId}`);
        }
        
        const envVar = configService.getEnvVar(profileId, key);
        if (!envVar) {
          throw new Error(`Environment variable not found: ${key}`);
        }
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                profileId,
                profileName: profile.name,
                key,
                value: envVar.sensitive ? '********' : envVar.value,
                sensitive: envVar.sensitive,
                description: envVar.description
              }, null, 2)
            }
          ]
        };
      }
    );
  • src/server.ts:31-31 (registration)
    High-level registration call to registerEnvironmentTools in the main server initialization, which includes the 'get-env-var' tool among environment management tools.
    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