alexa-mcp

Create Smart Home Group

alexa_create_group

Create a new Alexa smart home group or room by providing a name. Optionally assign appliance IDs to organize devices into that group.

Instructions

Create a new Alexa smart home group/room with a name and optional 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": {
      "name": "<name>"
    },
    "name": "alexa_create_group"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	The group/room name
`applianceIds`	No	List of appliance IDs to assign to this group

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 11, 2026

TDQS

A3.5/5.0

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. It states 'create' which implies mutation, but lacks details on permissions, idempotency, duplicate handling, or limits. For a mutation tool, more behavioral context is needed.

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 concise sentence that includes the key elements: action, resource, and parameters. No extraneous words, and it is front-loaded with the main purpose.

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 simplicity (2 simple parameters, no output schema, no annotations), the description provides the minimal necessary information. However, it lacks details about return values, constraints (e.g., group name uniqueness), and potential side effects, which could be useful for completeness.

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?

With 100% schema coverage, the baseline is 3. The description adds minimal value by summarizing 'name' and 'optional list of appliance IDs', but the schema already provides these details. No additional meaning beyond schema is provided.

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?

The description clearly states the action ('create') and the resource ('Alexa smart home group/room'), and includes details about the optional appliance list. This effectively distinguishes it from sibling tools like alexa_update_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 Guidelines3/5

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

The description implies when to use this tool (to create a group) but does not explicitly mention alternatives or when not to use it. The context from sibling names provides some guidance, but the description itself lacks explicit when-to-use or when-not-to-use guidance.

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