Skip to main content
Glama

get-device

Retrieve detailed information about a specific ESP8266/NodeMCU IoT device using its unique device ID. Integrates with REST/WebSocket APIs and the Model Context Protocol for streamlined IoT management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdYesThe ID of the device to get information about

Implementation Reference

  • Primary handler for the 'get-device' tool using the official MCP SDK. Validates the deviceId parameter using Zod schema and retrieves detailed device information from the DeviceManager.
    server.tool(
      "get-device",
      {
        deviceId: z.string().describe("The ID of the device to get information about")
      },
      async ({ deviceId }) => {
        try {
          if (!deviceId) {
            throw new Error('Device ID is required');
          }
          
          const device = deviceManager.getDevice(deviceId);
          
          if (!device) {
            throw new Error(`Device not found: ${deviceId}`);
          }
          
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify(device, null, 2)
            }]
          };
        } catch (error) {
          console.error('Error getting device:', error);
          throw new Error(`Failed to get device: ${error.message}`);
        }
      }
    );
  • Custom MCP server handler for the 'get-device' tool. Fetches and returns device details by ID from the DeviceManager.
    // Tool implementation: Get device details
    async getDevice(deviceId) {
      if (!deviceId) {
        throw new Error('Device ID is required');
      }
      
      const device = deviceManager.getDevice(deviceId);
      
      if (!device) {
        throw new Error(`Device not found: ${deviceId}`);
      }
      
      return device;
    }
  • Core helper method in DeviceManager that retrieves a device object by ID from the internal devices Map.
    getDevice(deviceId) {
      return this.devices.get(deviceId) || null;
    }
  • Input schema definition for the 'get-device' tool in the custom MCP server, specifying the required deviceId parameter.
    "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"
        }
      }
  • Zod-based input schema for the 'get-device' tool in the MCP SDK implementation.
    {
      deviceId: z.string().describe("The ID of the device to get information about")
    },
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/nodemcu-mcp'

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