Skip to main content
Glama
Sign In
alexa-mcp

alexa-mcp

by snordquist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List scenes / smart-home entities

alexa_list_scenes

List smart-home scenes from your Alexa account to use as routine actions. Optionally filter by name or type.

Instructions

Smart-home entities including scenes usable as routine actions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "alexa_list_scenes"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations present. Description does not disclose any behavioral traits (e.g., read-only, permissions, side effects). All burden on description, which provides nothing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is only a short phrase, lacking structure. While concise, it is under-specified and does not front-load the tool's action.

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

Completeness1/5

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

Given no output schema, no annotations, and minimal description, the tool's full functionality is unclear. No information on output format, filtering behavior, or how it differs from sibling tools.

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

Parameters1/5

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

Schema has 0% coverage for parameter 'filter'. Description does not mention or explain the filter parameter at all, leaving the agent without guidance on how to use it.

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

Purpose2/5

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

Description is vague: 'Smart-home entities including scenes usable as routine actions' does not clearly state that the tool lists scenes. It relies on the title for context, which is insufficient for standalone clarity.

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

Usage Guidelines1/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 over siblings like alexa_list_routines or alexa_list_smarthome_devices. Missing 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