Skip to main content
Glama
Allentgt

dynamodb-mcp-server

by Allentgt

update_item

Idempotent

Update specific attributes of an existing DynamoDB item without replacing the whole item, using SET, REMOVE, ADD, or DELETE operations.

Instructions

Update specific attributes of an item in a DynamoDB table.

Modifies only the specified attributes without replacing the entire item. Supports SET, REMOVE, ADD, and DELETE operations in the update expression. Returns the updated item's attributes.

When to use:

  • To modify specific attributes of an existing item

  • To increment counters (SET count = count + :inc)

  • To add/remove elements from sets

  • To remove attributes from an item

When NOT to use:

  • To replace an entire item (use add_item instead)

  • To update many items at once (iterate with update_item or use bulk operations)

Returns: JSON with the updated item attributes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

The description explicitly encourages non-idempotent operations such as 'SET count = count + :inc' and ADD, but annotations declare idempotentHint=true. This is a direct contradiction, undermining trust in the tool's behavioral contract.

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 well-structured with a clear lead, bullet lists for usage, and a returns section. Every sentence serves a purpose, and the length is appropriate for the tool's complexity.

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?

Combined with a rich schema and output schema, the description covers core selection, supported operations, and the return format. It would be a 5 if not for the idempotency contradiction and the omission that UpdateItem can create an item if the key does not exist.

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?

Even though schema description coverage is reported as 0%, the description gives practical examples of update expression syntax and supported operations (SET, REMOVE, ADD, DELETE). It does not elaborate on condition_expression or expression_attribute_names, but those are described 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 first sentence clearly specifies the verb ('Update') and the resource ('specific attributes of an item in a DynamoDB table'), and adds scope by noting it does not replace the entire item. This distinguishes it from sibling tools like add_item and delete_item.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Dedicated 'When to use' and 'When NOT to use' sections provide explicit selection guidance. It names add_item for full item replacement and bulk operations for multi-item updates, directly addressing alternatives.

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/Allentgt/dynamodb-mcp-server'

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