alexa-mcp

Update Smart Home Group

alexa_update_group

Update an existing Alexa smart home group or room by setting its name and complete list of appliance IDs. Requires the group ID from alexa_list_groups.

Instructions

Update an existing Alexa smart home group/room. Sets the name and full list of appliance IDs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "groupId": "<groupId>",
      "name": "<name>",
      "applianceIds": "<applianceIds>"
    },
    "name": "alexa_update_group"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The group/room name
`groupId`	Yes	The group ID (from alexa_list_groups)
`applianceIds`	Yes	Full list of appliance IDs to assign to this group

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 11, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so the description carries full burden. It discloses that the update sets name and appliance IDs, implying overwrite, but lacks details on reversibility, permissions, or side effects. Adequate but 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?

Single sentence, no redundancy, directly states action and what it updates. Efficient and easy to parse.

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

Completeness4/5

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

Given 3 parameters, no output schema, and no annotations, the description adequately covers purpose and parameter semantics. Missing behavioral details about return value, but sufficient for a simple update tool.

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?

Schema covers 100% of parameters, baseline 3. The description adds value by stating 'full list' of appliance IDs, clarifying that it's a complete replacement. This semantic nuance goes beyond the schema.

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

Purpose5/5

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

Description clearly states 'Update an existing Alexa smart home group/room' and specifies what it sets (name and full list of appliance IDs). This distinguishes it from sibling tools like alexa_create_group and alexa_delete_group.

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

Usage Guidelines4/5

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

The description implies use for modifying an existing group, but does not explicitly state when not to use it or mention alternatives. However, the sibling tool names provide context that create_group is for creation, so it is fairly clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.