Skip to main content
Glama

dynamodb_item_get

Retrieve specific items from Amazon DynamoDB tables using primary keys to access stored data for analysis or processing.

Instructions

Get an item from a DynamoDB table

Input Schema

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

Implementation Reference

  • Handler logic for the 'dynamodb_item_get' tool. Calls boto3 dynamodb_client.get_item() with the provided table_name and key from arguments.
    elif name == "dynamodb_item_get":
        response = dynamodb_client.get_item(
            TableName=arguments["table_name"],
            Key=arguments["key"]
        )
  • Input schema definition for the 'dynamodb_item_get' tool, specifying table_name (string) and key (object) as required parameters.
    Tool(
        name="dynamodb_item_get",
        description="Get an item from 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"
                }
            },
            "required": ["table_name", "key"]
        }
    ),
  • Registers the 'dynamodb_item_get' tool (among others) via the MCP server.list_tools() handler 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?

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states it's a read operation ('Get'), but doesn't cover error handling, permissions needed, performance characteristics, or what happens if the item doesn't exist. For a database operation with no annotation coverage, this is insufficient.

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 that gets straight to the point with zero wasted words. It's appropriately sized for a simple retrieval operation.

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?

For a database read operation with no annotations and no output schema, the description is inadequate. It doesn't explain what format the returned item will be in, what happens on errors, or any constraints like required IAM permissions. Given the complexity of DynamoDB operations, more context is needed.

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?

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description doesn't add any additional meaning about the parameters beyond what's in the schema, meeting the baseline for high schema coverage.

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 ('Get') and resource ('an item from a DynamoDB table'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like dynamodb_item_query or dynamodb_item_scan, which also retrieve items but with different approaches.

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 is provided on when to use this tool versus alternatives. The description doesn't mention that this is for retrieving a single item by its exact key, as opposed to querying or scanning for multiple items, which are available as sibling tools.

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