alexa-mcp

Speak Text

alexa_speak

Make Alexa speak plain text on a specific Echo device using native text-to-speech without an announcement chime. Provide the device serial number or name and the text to speak.

Instructions

Make Alexa speak plain text directly on a specific Echo device using native text-to-speech (no announcement chime).

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": {
      "serialNumber": "<serialNumber>",
      "text": "<text>"
    },
    "name": "alexa_speak"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	The text for Alexa to speak
`serialNumber`	Yes	Serial number or name of the Echo device (e.g. "Piano", "Living Room")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It does add one genuinely useful behavioral trait beyond the name: playback is direct TTS with no announcement chime, which distinguishes audible behavior from alexa_announce. However, it says nothing about whether the call blocks until speech finishes, device-online requirements, or failure behavior.

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?

A single front-loaded sentence with no filler; the differentiating clause (no announcement chime) is placed at the end where it is easy to scan. Every element earns its place.

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?

For a simple two-parameter, no-output-schema tool this is nearly complete: the action, target device type, and audio behavior are all covered. The only gap is guidance on choosing between this, alexa_speak_ssml, and alexa_announce.

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?

Schema description coverage is 100%, so both parameters (text, serialNumber) are already documented in the schema, including the name-or-serial flexibility. The description mentions 'plain text' and 'a specific Echo device' but adds no format or constraint detail beyond the schema, so the baseline of 3 applies.

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 gives a precise verb ('Make Alexa speak') plus resource ('plain text ... on a specific Echo device') and pins the modality with 'native text-to-speech (no announcement chime)'. The parenthetical implicitly separates it from alexa_announce and alexa_speak_ssml, so an agent can place it among siblings without opening the schema.

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?

Usage is only implied: 'plain text' and 'no announcement chime' hint that SSML belongs to alexa_speak_ssml and that a chime means alexa_announce, but neither sibling is named and no when-to-use condition is stated. The agent must infer routing from a parenthetical rather than explicit guidance.

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