Skip to main content
Glama

get_effects

Retrieve available lighting effects for Nanoleaf smart lights to customize illumination patterns and enhance ambiance.

Instructions

Get list of available effects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP server tool handler for the 'get_effects' tool. It calls getEffects() on the NanoleafClient instance and returns the list of effects as JSON text content.
    case 'get_effects':
      const effects = await primaryDevice.getEffects();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(effects, null, 2),
          },
        ],
      };
  • Core implementation of getEffects method in NanoleafClient class. Fetches the list of available effects from the Nanoleaf device API endpoint '/effects/effectsList'.
    async getEffects(): Promise<string[]> {
      const response = await this.httpClient.get(this.getAuthUrl('/effects/effectsList'));
      return response.data;
    }
  • src/index.ts:133-140 (registration)
    Registration of the 'get_effects' tool in the MCP server's listTools response, including name, description, and input schema (no parameters required).
    {
      name: 'get_effects',
      description: 'Get list of available effects',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema for 'get_effects' tool: empty object (no input parameters). Note: output is not explicitly schemed.
    {
      name: 'get_effects',
      description: 'Get list of available effects',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
Behavior2/5

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

With no annotations, the description carries full burden but only states it 'gets' a list, implying a read-only operation. It lacks details on behavior such as whether it returns all effects, if there's pagination, error handling, or if it requires prior setup (e.g., connection). No contradictions exist, but it's minimal.

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, efficient sentence with no wasted words. It's front-loaded and directly states the tool's function, making it highly concise and well-structured for its simplicity.

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

Completeness3/5

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

Given the tool's low complexity (0 parameters, no output schema), the description is minimally adequate. However, it lacks context about the Nanoleaf system (e.g., that effects are for lighting) and doesn't explain the return format, which could be important since there's no output schema.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, but this is acceptable given the schema's completeness, warranting a baseline score above 3 for a parameterless tool.

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 verb ('Get') and resource ('list of available effects'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_nanoleaf_info' or specify what 'effects' are in this context (e.g., visual effects for Nanoleaf lights).

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether authorization or connection is needed first), nor does it clarify if this is for querying effects before applying them with 'set_effect'.

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