Skip to main content
Glama

list-devices

Retrieve a list of NodeMCU/ESP8266 IoT devices managed by the NodeMCU MCP Service for remote control and AI-assisted integration. Simplify device monitoring and management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for 'list-devices' tool using official MCP SDK. Calls deviceManager.getAllDevices() and formats response as MCP content.
    server.tool(
      "list-devices",
      {}, // No parameters required
      async () => {
        try {
          const devices = deviceManager.getAllDevices();
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({
                devices: devices.map(device => ({
                  id: device.id,
                  name: device.name,
                  status: device.status,
                  lastSeen: device.lastSeen
                })),
                count: devices.length
              }, null, 2)
            }]
          };
        } catch (error) {
          console.error('Error listing devices:', error);
          throw new Error(`Failed to list devices: ${error.message}`);
        }
      }
    );
  • Handler function listDevices() in custom MCP server implementation. Fetches and maps devices from DeviceManager.
    async listDevices() {
      const devices = deviceManager.getAllDevices();
      return {
        devices: devices.map(device => ({
          id: device.id,
          name: device.name,
          status: device.status,
          lastSeen: device.lastSeen
        })),
        count: devices.length
      };
    }
  • Schema definition for 'list-devices' tool in custom implementation (no parameters, description provided).
    "list-devices": {
      description: "List all registered NodeMCU devices and their status",
      parameters: {}
    },
  • mcp_server.js:13-57 (registration)
    Tool definitions object including registration of 'list-devices' sent during MCP initialization.
    this.toolDefinitions = {
      "list-devices": {
        description: "List all registered NodeMCU devices and their status",
        parameters: {}
      },
      "get-device": {
        description: "Get detailed information about a specific NodeMCU device",
        parameters: {
          deviceId: {
            type: "string",
            description: "The ID of the device to get information about"
          }
        }
      },
      "send-command": {
        description: "Send a command to a NodeMCU device",
        parameters: {
          deviceId: {
            type: "string",
            description: "The ID of the device to send the command to"
          },
          command: {
            type: "string",
            description: "The command to send (restart, update, status, etc.)"
          },
          params: {
            type: "object",
            description: "Optional parameters for the command"
          }
        }
      },
      "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"
          }
        }
      }
    };
  • Core helper method getAllDevices() in DeviceManager that returns all tracked devices.
    getAllDevices() {
      return Array.from(this.devices.values());
    }
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