Skip to main content
Glama
kaeljune

Fibaro HC3 MCP Server

by kaeljune

fibaro_stop_scene

Stop a running scene on your Fibaro Home Center 3 smart home system by specifying the scene ID.

Instructions

Stop a running scene

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesScene ID to stop

Implementation Reference

  • MCP tool handler for fibaro_stop_scene: validates connection, extracts scene ID from args, calls fibaroClient.stopScene, and returns success message.
    case 'fibaro_stop_scene': {
      if (!this.fibaroClient) {
        throw new Error('Not connected to Fibaro HC3. Please check your configuration and restart the MCP server.');
      }
      const sceneId = args?.id as number;
      await this.fibaroClient.stopScene(sceneId);
      return {
        content: [
          {
            type: 'text',
            text: `Successfully stopped scene ${sceneId}`,
          },
        ],
      };
    }
  • src/index.ts:316-328 (registration)
    Tool registration including name, description, and input schema definition (requires scene ID). Part of the tools array passed to server.setTools.
      name: 'fibaro_stop_scene',
      description: 'Stop a running scene',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'number',
            description: 'Scene ID to stop',
          },
        },
        required: ['id'],
      },
    },
  • Core implementation: sends POST request to Fibaro HC3 API endpoint /api/scenes/{id}/action/stop to stop the scene.
    async stopScene(id: number): Promise<void> {
      try {
        await this.client.post(`/api/scenes/${id}/action/stop`, {
          args: []
        });
      } catch (error) {
        throw new Error(`Failed to stop scene ${id}: ${error}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Stop') but lacks details on permissions required, whether the operation is reversible, error conditions (e.g., if the scene isn't running), or response behavior. This is a significant gap for a mutation tool.

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 zero waste. It is front-loaded with the core action and target, making it highly concise and well-structured for quick understanding.

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 tool's complexity (a mutation operation to stop scenes), lack of annotations, and no output schema, the description is incomplete. It fails to address behavioral aspects like error handling, permissions, or what happens after stopping a scene, leaving gaps that could hinder effective agent use.

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

Parameters3/5

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

The schema description coverage is 100%, with the single parameter 'id' documented as 'Scene ID to stop'. The description adds no additional meaning beyond this, such as format examples or where to obtain valid IDs. The baseline score of 3 is appropriate since the schema handles the parameter documentation adequately.

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 ('Stop') and target ('a running scene'), providing a specific verb+resource combination. It distinguishes itself from siblings like 'fibaro_run_scene' by indicating the opposite action, though it doesn't explicitly mention sibling differentiation in the text.

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 doesn't specify prerequisites (e.g., that a scene must be running), mention related tools like 'fibaro_get_scene' for checking status, or indicate any exclusions or context for usage.

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/kaeljune/fibaro-mcp-server'

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