Skip to main content
Glama
Sign In
alexa-mcp

alexa-mcp

by serversmx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Set Do Not Disturb

alexa_do_not_disturb

Enable or disable Do Not Disturb mode on a chosen Echo device to silence notifications and alerts when needed.

Instructions

Enable or disable Do Not Disturb on a specific Echo device.

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>",
      "enabled": "<enabled>"
    },
    "name": "alexa_do_not_disturb"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue to enable DND, false to disable
serialNumberYesSerial number of the Echo device

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

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 full burden. It discloses the core effect (enable/disable DND) but omits details like whether the change is immediate, persists, or requires network connectivity. For a simple toggle, it is minimally adequate.

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 short sentence with no wasted words. It is front-loaded and efficient.

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 tool with 2 parameters and no output schema, the description is largely complete. It could mention that the serial number must be obtained from alexa_list_devices, but this is a minor gap.

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 clear descriptions for both parameters. The description adds no semantic value beyond the schema; it simply repeats the context of 'specific Echo device'.

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 verb 'Enable or disable' and the resource 'Do Not Disturb on a specific Echo device'. It uniquely identifies the tool among siblings, as no other tool handles DND.

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 does not provide explicit guidance on when to use this tool vs alternatives, nor does it mention prerequisites or when not to use it. However, since it is the only DND tool among siblings, usage is implied.

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