Skip to main content
Glama
Sign In
alexa-mcp

alexa-mcp

by snordquist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Activity history

alexa_get_activity

Retrieves Amazon Alexa activity history to confirm when routines or commands were triggered. Filter by time range and record type.

Instructions

Activity history (customer-history-records-v2). Shows what fired when — useful to confirm when a routine or command was triggered.

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

Input Schema

NameRequiredDescriptionDefault
endTimeMsNo
recordTypeNo
startTimeMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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. Only says 'Shows what fired when' without detailing read-only nature, rate limits, pagination, or authentication needs.

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

Conciseness4/5

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

Single concise sentence with additional parenthetical identifier. Front-loaded with purpose, but very brief. Could add more value without losing conciseness.

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?

No output schema, no annotations, and 3 undocumented parameters. Description is too minimal to fully equip an AI agent for correct invocation. Missing details on response format, filtering, and constraints.

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 3 parameters with 0% description coverage. Description does not explain any parameter meaning, format, or usage beyond field names (endTimeMs, recordType, startTimeMs).

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?

Clearly states the tool retrieves activity history to confirm when routines or commands were triggered. Distinguishes from siblings (routines, devices, scenes) by focusing on activity log.

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?

Implies use for verifying triggers, but no explicit when-to-use or when-not-to-use. Sibling tools are listed but no guidance on choosing between them.

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