Skip to main content
Glama
devlimelabs

MCP Environment & Installation Manager

by devlimelabs

update-profile

Modify an existing profile's name and description in the MCP Environment & Installation Manager to adjust configuration settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileIdYesProfile ID to update
nameNoNew name for the profile
descriptionNoNew description for the profile

Implementation Reference

  • The handler function for the 'update-profile' tool. It validates the profileId and name if provided, constructs updates object, calls configService.updateProfile, and returns a JSON response with the updated profile.
    async ({ profileId, name, description }, extra) => {
      if (!profileId.trim()) {
        throw new Error("Profile ID cannot be empty");
      }
      
      if (name !== undefined && !name.trim()) {
        throw new Error("Profile name cannot be empty");
      }
      
      const updates: { name?: string; description?: string } = {};
      
      if (name !== undefined) {
        updates.name = name;
      }
      
      if (description !== undefined) {
        updates.description = description;
      }
      
      const profile = await configService.updateProfile(profileId, updates);
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              success: true,
              profile
            }, null, 2)
          }
        ]
      };
    }
  • Zod input schema defining parameters for the update-profile tool: required profileId, optional name and description.
    {
      profileId: z.string().describe("Profile ID to update"),
      name: z.string().optional().describe("New name for the profile"),
      description: z.string().optional().describe("New description for the profile")
    },
  • Registration of the 'update-profile' tool using server.tool(), specifying name, input schema, and handler function within registerProfileTools.
    server.tool(
      "update-profile",
      {
        profileId: z.string().describe("Profile ID to update"),
        name: z.string().optional().describe("New name for the profile"),
        description: z.string().optional().describe("New description for the profile")
      },
      async ({ profileId, name, description }, extra) => {
        if (!profileId.trim()) {
          throw new Error("Profile ID cannot be empty");
        }
        
        if (name !== undefined && !name.trim()) {
          throw new Error("Profile name cannot be empty");
        }
        
        const updates: { name?: string; description?: string } = {};
        
        if (name !== undefined) {
          updates.name = name;
        }
        
        if (description !== undefined) {
          updates.description = description;
        }
        
        const profile = await configService.updateProfile(profileId, updates);
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: true,
                profile
              }, null, 2)
            }
          ]
        };
      }
    );
  • Helper method in ConfigService that performs the actual profile update by modifying the in-memory profiles config and persisting to disk.
    async updateProfile(id: string, updates: Partial<Pick<Profile, 'name' | 'description'>>): Promise<Profile> {
      const profileIndex = this.profilesConfig.profiles.findIndex(p => p.id === id);
      if (profileIndex === -1) {
        throw new Error(`Profile not found: ${id}`);
      }
      
      const profile = this.profilesConfig.profiles[profileIndex];
      const updatedProfile = {
        ...profile,
        ...updates,
        updatedAt: new Date().toISOString()
      };
      
      this.profilesConfig.profiles[profileIndex] = updatedProfile;
      await this.saveProfiles();
      
      return updatedProfile;
    }
  • src/server.ts:32-32 (registration)
    Top-level call to registerProfileTools in initializeServer, which registers all profile tools including 'update-profile'.
    registerProfileTools(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