Skip to main content
Glama

dynamodb_item_update

Modify existing items in DynamoDB tables by specifying table name, item key, and updated data attributes.

Instructions

Update an item in a DynamoDB table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_nameYesName of the DynamoDB table
keyYesKey to identify the item
itemYesUpdated item data

Implementation Reference

  • Executes the dynamodb_item_update tool by invoking the DynamoDB boto3 client's update_item method with the provided table_name, key, and AttributeUpdates=item from the arguments.
    elif name == "dynamodb_item_update":
        response = dynamodb_client.update_item(
            TableName=arguments["table_name"],
            Key=arguments["key"],
            AttributeUpdates=arguments["item"]
        )
  • Defines the Tool object for dynamodb_item_update, including its input schema requiring table_name (string), key (object), and item (object). This is used for validation and returned in list_tools.
    Tool(
        name="dynamodb_item_update",
        description="Update an item in a DynamoDB table",
        inputSchema={
            "type": "object",
            "properties": {
                "table_name": {
                    "type": "string",
                    "description": "Name of the DynamoDB table"
                },
                "key": {
                    "type": "object",
                    "description": "Key to identify the item"
                },
                "item": {
                    "type": "object",
                    "description": "Updated item data"
                }
            },
            "required": ["table_name", "key", "item"]
        }
    ),
  • Registers the dynamodb_item_update tool (among others) with the MCP server by returning get_aws_tools() which includes it.
    async def list_tools() -> list[Tool]:
        """List available AWS tools"""
        logger.debug("Handling list_tools request")
        return get_aws_tools()
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 of behavioral disclosure. While 'Update' implies a mutation, it lacks details on permissions needed, whether it's idempotent, error handling (e.g., if the item doesn't exist), or side effects. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence with zero waste. It is front-loaded and directly communicates the core functionality without unnecessary elaboration.

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?

Given the complexity of a DynamoDB update operation, no annotations, and no output schema, the description is insufficient. It should address behavioral aspects like atomic updates, conditional writes, or return values to help an agent use it correctly.

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

Parameters3/5

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

The schema description coverage is 100%, with clear descriptions for 'table_name', 'key', and 'item'. The description does not add any semantic details beyond what the schema provides, such as explaining how 'key' identifies the item or what 'item' should contain. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the action ('Update') and resource ('an item in a DynamoDB table'), making the purpose immediately understandable. However, it does not differentiate this tool from its sibling 'dynamodb_item_put' or 'dynamodb_table_update', which could cause confusion about when to use each.

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?

The description provides no guidance on when to use this tool versus alternatives like 'dynamodb_item_put' (for creating/overwriting items) or 'dynamodb_table_update' (for modifying table settings). Without such context, an agent might misuse the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rishikavikondala/mcp-server-aws'

If you have feedback or need assistance with the MCP directory API, please join our Discord server