Skip to main content
Glama
Sign In
alexa-mcp

alexa-mcp

by GraysonCAdams
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Complete Shopping Items

complete_items

Mark items as done on your Alexa shopping list by providing their names. Uses case-insensitive matching to identify and complete them.

Instructions

Mark items as completed on your Alexa shopping list by name (case-insensitive match).

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": {
      "names": "<names>"
    },
    "name": "complete_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesItem names to mark as completed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It reveals the case-insensitive matching behavior but omits details about side effects, authorization needs, or what happens if an item is not found. Adequate but not comprehensive.

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?

Single sentence, no fluff. Every word adds value. Appropriate for a simple tool.

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

Completeness3/5

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

Given no output schema and no annotations, the description covers the core action but lacks usage guidelines, error handling details, and return value explanation. Adequate for a straightforward tool but missing context.

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?

Schema description coverage is 100% (parameter 'names' has a description). The description adds valuable context beyond the schema by specifying 'case-insensitive match' and 'by name', which is not in the input schema.

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 action ('Mark items as completed'), the resource ('on your Alexa shopping list'), and a key behavior ('by name (case-insensitive match)'). It effectively differentiates from sibling tools like delete_items or add_items.

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 vs alternatives like delete_items or update_item. The description does not mention prerequisites, error conditions, or typical use cases.

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