Skip to main content
Glama

update-config

Modify configuration settings for specific NodeMCU/ESP8266 IoT devices remotely via the NodeMCU MCP Service, ensuring efficient device management and control.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configYesConfiguration parameters to update
deviceIdYesThe ID of the device to update configuration for

Implementation Reference

  • Primary handler implementation using official MCP SDK. Registers the tool with Zod schema validation and executes by calling deviceManager.updateDeviceConfig, returning formatted response.
    server.tool(
      "update-config",
      {
        deviceId: z.string().describe("The ID of the device to update configuration for"),
        config: z.record(z.any()).describe("Configuration parameters to update")
      },
      async ({ deviceId, config }) => {
        try {
          if (!deviceId) {
            throw new Error('Device ID is required');
          }
          
          if (!config || Object.keys(config).length === 0) {
            throw new Error('Configuration is required');
          }
          
          const result = await deviceManager.updateDeviceConfig(deviceId, config);
          
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({
                success: true,
                deviceId,
                updatedConfig: result
              }, null, 2)
            }]
          };
        } catch (error) {
          console.error('Error updating config:', error);
          throw new Error(`Failed to update configuration: ${error.message}`);
        }
      }
    );
  • Alternative custom handler for update-config tool execution, delegates to deviceManager.
    // Tool implementation: Update device configuration
    async updateConfig(deviceId, config) {
      if (!deviceId) {
        throw new Error('Device ID is required');
      }
      
      if (!config || Object.keys(config).length === 0) {
        throw new Error('Configuration is required');
      }
      
      try {
        return await deviceManager.updateDeviceConfig(deviceId, config);
      } catch (error) {
        throw new Error(`Failed to update configuration: ${error.message}`);
      }
    }
  • Core helper method that implements config update by sending a 'config' command over WebSocket and updating local device state.
    async updateDeviceConfig(deviceId, config = {}) {
      try {
        const result = await this.sendCommand(deviceId, 'config', config);
        
        // Update stored device config
        if (this.devices.has(deviceId)) {
          const device = this.devices.get(deviceId);
          device.config = {
            ...device.config,
            ...config
          };
          this.devices.set(deviceId, device);
        }
        
        return result;
      } catch (error) {
        throw error;
      }
    }
  • Tool schema definition for update-config in custom server.
    "update-config": {
      description: "Update the configuration of a NodeMCU device",
      parameters: {
        deviceId: {
          type: "string",
          description: "The ID of the device to update configuration for"
        },
        config: {
          type: "object",
          description: "Configuration parameters to update"
        }
      }
    }
  • Zod schema for update-config parameters in SDK implementation.
    {
      deviceId: z.string().describe("The ID of the device to update configuration for"),
      config: z.record(z.any()).describe("Configuration parameters to update")
    },
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

Related 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/amanasmuei/mcp-server-nodemcu'

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