Skip to main content
Glama
Sign In
alexa-mcp

alexa-mcp

by serversmx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Speak SSML

alexa_speak_ssml

Send SSML commands to any Echo device to control Alexa's speech with pauses, emphasis, and more for custom voice interactions.

Instructions

Make Alexa speak using SSML (Speech Synthesis Markup Language) for advanced voice control.

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>",
      "ssml": "<ssml>"
    },
    "name": "alexa_speak_ssml"
  }
}

Input Schema

NameRequiredDescriptionDefault
ssmlYesSSML content (e.g., "<speak>Hello <break time=\"1s\"/> World</speak>")
serialNumberYesSerial number of the Echo device

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose whether the call is synchronous, error handling, or requirements like device availability. Only implies speaking action.

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?

Two sentences that concisely state purpose and key detail. No redundant or extraneous information.

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

Completeness2/5

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

Given two required parameters and no output schema or annotations, the description lacks critical context such as SSML syntax requirements, device targeting nuances, and expected behavior.

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 coverage is 100% with both parameters described. Description does not add additional meaning beyond the schema, so baseline score of 3 applies.

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

Purpose4/5

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

Clearly states the tool makes Alexa speak using SSML for advanced voice control. However, it does not differentiate from siblings like alexa_announce which may handle plain text announcements.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as alexa_announce or alexa_text_command. The description does not provide any context for selection.

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