Skip to main content
Glama
Sign In
alexa-mcp

alexa-mcp

by snordquist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List Alexa devices

alexa_list_devices

List all registered Alexa devices including Echos, apps, and Fire TVs with their name, type, and serial number.

Instructions

All registered Echos / apps / Fire TVs (name, type, serial number).

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_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool lists devices and returns fields, but it does not disclose any behavioral traits such as read-only nature, required permissions, or possible limitations. For a list operation, the behavioral transparency is minimal.

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 sentence that efficiently conveys the purpose and output fields. No unnecessary words. Front-loaded and concise.

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?

Given the tool has no parameters and no output schema, the description is fairly complete. It tells what it lists and what fields are returned. However, it could benefit from clarifying 'apps' or noting that it returns all registered devices. Still, adequate for its simplicity.

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

Parameters4/5

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

There are zero parameters, and schema coverage is 100%. According to calibration guidelines, zero parameters baseline is 4. The description adds no parameter info, but none is needed.

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 'list' and the resource 'registered Echos / apps / Fire TVs' along with the returned fields (name, type, serial number). It distinguishes itself from sibling tools like alexa_list_smarthome_devices by focusing on Alexa devices specifically.

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 when-to-use or when-not-to-use instructions. The scope is implied by naming and description, but no alternatives or prerequisites are mentioned. The tool is simple enough that usage is intuitive, but lack of explicit guidance prevents a higher score.

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