Skip to main content
Glama
Sign In
alexa-mcp

alexa-mcp

by GraysonCAdams
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Update Shopping Item

update_item

Update an item on your Alexa shopping list by renaming it or changing its completion status.

Instructions

Update an item on your Alexa shopping list by name (case-insensitive). Can rename and/or change completion status.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCurrent item name (case-insensitive)
new_nameNoNew name for the item
completedNoSet completion status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Description adds value beyond annotations by clarifying case-insensitive name matching and the ability to rename and change status. However, it does not disclose side effects, authorization requirements, or rate limits. Annotations only provide destructiveHint=false, so description carries moderate burden.

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?

Two sentences, front-loaded with the action and key details. Every sentence adds value without redundancy. Highly 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?

Given the simplicity of the tool and full schema coverage, the description is fairly complete. It lacks information about return values (e.g., confirmation or updated item details) but covers core functionality. Sibling list provides external 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 coverage is 100% with parameter descriptions, so baseline is 3. Description adds context by explaining how the 'name' parameter is used for lookup (case-insensitive) and that 'new_name' and 'completed' relate to rename and completion status, respectively.

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?

Description clearly states the action ('Update an item on your Alexa shopping list by name') and provides specifics (case-insensitive, can rename and/or change completion status). It distinguishes from siblings like add_items and delete_items by focusing on modifying existing 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 explicit guidance on when to use this tool versus alternatives (e.g., add_items for new items, complete_items for completion only). The description implies use for updating by name but does not exclude cases or provide 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