Skip to main content
Glama
Sign In
alexa-mcp

alexa-mcp

by snordquist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Inspect an Alexa routine

alexa_get_routine

Retrieve a single Alexa routine's full JSON structure and action sequence by providing its automation ID.

Instructions

Raw JSON of one routine (incl. action sequence) by automationId.

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": {
      "automationId": "<automationId>"
    },
    "name": "alexa_get_routine"
  }
}

Input Schema

NameRequiredDescriptionDefault
automationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The description notes it returns 'Raw JSON' including action sequence, which gives some behavioral insight. However, no annotations are provided, and the description does not disclose any other traits (e.g., read-only nature, permission requirements).

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 conveys the essential information without unnecessary words.

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 (1 parameter, no output schema), the description is roughly adequate but could be improved by mentioning error conditions or the exact return structure beyond 'raw JSON'.

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

Parameters2/5

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

The only parameter 'automationId' is not explained beyond its name. The schema has 0% description coverage, and the description adds no semantic context about where to find the ID or its format.

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 states 'Raw JSON of one routine (incl. action sequence) by automationId.' It clearly specifies the resource (routine), the action (get), and is distinct from siblings like alexa_list_routines which lists multiple routines.

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?

No explicit guidance on when to use this versus alternatives. It implies usage when a specific automationId is known, but does not mention when not to use it or point to siblings like alexa_list_routines for listing.

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

Deploy Server

Other Tools