alexa-mcp

Execute Alexa Routine

alexa_execute_routine

Trigger an Alexa routine by supplying its automation definition, typically the routine object returned by alexa_list_routines.

Instructions

Execute an existing Alexa routine by providing its automation definition (from alexa_list_routines).

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": {
      "routine": "<routine>"
    },
    "name": "alexa_execute_routine"
  }
}

Input Schema

Name	Required	Description	Default
`routine`	Yes	The full routine/automation object as returned by alexa_list_routines

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. Description discloses the action (execute) but does not describe side effects, required permissions, error handling, or networking behavior. Minimal additional context beyond the action itself.

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, front-loaded with the action, no unnecessary words. Efficient and direct.

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?

Simple tool with one parameter and no output schema. Description covers the essential purpose and input source. Lacks details on return value or execution results, but acceptable for a straightforward action.

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 single parameter 'routine' has a schema description and the tool description adds that it must be the full object from alexa_list_routines, providing useful context 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?

Clear verb 'Execute' and specific resource 'Alexa routine'. Explicitly references the source of the routine object from alexa_list_routines, distinguishing it from sibling tools.

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?

States that the routine definition should come from alexa_list_routines, implying correct usage. While explicit when-not-to-use is absent, among siblings only this tool executes routines, so it is adequately clear.

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