Skip to main content
Glama

get_nanoleaf_info

Retrieve device information from Nanoleaf smart lights to check status, connectivity, and available features for control.

Instructions

Get information about the Nanoleaf device

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_nanoleaf_info' that calls primaryDevice.getInfo() and returns the JSON-stringified device information.
    case 'get_nanoleaf_info':
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(await primaryDevice.getInfo(), null, 2),
          },
        ],
      };
  • src/index.ts:58-64 (registration)
    Registration of the 'get_nanoleaf_info' tool in the ListToolsRequestHandler, defining its name, description, and empty input schema.
      name: 'get_nanoleaf_info',
      description: 'Get information about the Nanoleaf device',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • TypeScript interface defining the structure of the NanoleafInfo response object returned by the tool.
    export interface NanoleafInfo {
      name: string;
      serialNo: string;
      manufacturer: string;
      firmwareVersion: string;
      model: string;
      state: {
        on: {
          value: boolean;
        };
        brightness: {
          value: number;
          max: number;
          min: number;
        };
        hue: {
          value: number;
          max: number;
          min: number;
        };
        sat: {
          value: number;
          max: number;
          min: number;
        };
        ct: {
          value: number;
          max: number;
          min: number;
        };
        colorMode: string;
      };
      effects: {
        select: string;
        effectsList: string[];
      };
      panelLayout: any;
    }
  • Core implementation of getInfo() in NanoleafClient class, which performs an authenticated GET request to the Nanoleaf API root endpoint and returns the device info.
    async getInfo(): Promise<NanoleafInfo> {
      const response = await this.httpClient.get(this.getAuthUrl(''));
      return response.data;
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Get information,' implying a read-only operation, but does not specify what information is returned, potential errors (e.g., if device is offline), or any side effects. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and reliability.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no wasted words. It is front-loaded with the core purpose ('Get information about the Nanoleaf device'), making it easy to parse. Every part of the sentence contributes directly to understanding the tool's function, achieving ideal conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is insufficient for a complete understanding. It does not explain what information is retrieved (e.g., device state, settings, capabilities) or the return format, leaving the agent uncertain about the tool's output. For a tool with no structured output documentation, the description should compensate more to ensure usability.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description does not need to add parameter details, as there are none to explain. It appropriately avoids unnecessary parameter information, earning a high baseline score for parameter clarity in this context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get information') and target resource ('Nanoleaf device'), making the purpose understandable. It distinguishes from siblings like 'get_effects' or 'set_brightness' by focusing on general device info rather than specific attributes or controls. However, it lacks specificity about what information is retrieved (e.g., device status, settings, capabilities), which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., device must be connected or authorized), nor does it differentiate from siblings like 'discover_nanoleaf' (for finding devices) or 'get_effects' (for listing effects). Without such context, the agent must infer usage from tool names alone.

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/srnetadmin/nanoleaf-mcp-server'

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