Skip to main content
Glama

dynamodb_table_create

Create a new DynamoDB table by specifying table name, key schema, and attribute definitions for AWS database setup.

Instructions

Create a new DynamoDB table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_nameYesName of the DynamoDB table
key_schemaYesKey schema for table creation
attribute_definitionsYesAttribute definitions for table creation

Implementation Reference

  • Executes the dynamodb_table_create tool by calling the AWS DynamoDB create_table API with the provided table_name, key_schema, and attribute_definitions, using pay-per-request billing.
    if name == "dynamodb_table_create":
        response = dynamodb_client.create_table(
            TableName=arguments["table_name"],
            KeySchema=arguments["key_schema"],
            AttributeDefinitions=arguments["attribute_definitions"],
            BillingMode="PAY_PER_REQUEST"
        )
  • Defines the Tool object including input schema validation for dynamodb_table_create.
        name="dynamodb_table_create",
        description="Create a new DynamoDB table",
        inputSchema={
            "type": "object",
            "properties": {
                "table_name": {
                    "type": "string",
                    "description": "Name of the DynamoDB table"
                },
                "key_schema": {
                    "type": "array",
                    "description": "Key schema for table creation"
                },
                "attribute_definitions": {
                    "type": "array",
                    "description": "Attribute definitions for table creation"
                }
            },
            "required": ["table_name", "key_schema", "attribute_definitions"]
        }
    ),
  • Registers all AWS tools, including dynamodb_table_create, via the MCP server.list_tools() handler by returning get_aws_tools().
    @server.list_tools()
    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 the full burden of behavioral disclosure. It states 'Create' which implies a write/mutation operation, but doesn't cover critical aspects like whether this is idempotent, what permissions are required, potential costs, rate limits, or what happens on failure (e.g., if the table already exists). For a cloud resource creation tool, this is a significant gap in transparency.

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 states the core purpose without any wasted words. It's appropriately sized for a tool with a clear name and well-documented schema, making it easy for an agent to parse quickly.

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 creating a DynamoDB table (a cloud resource with cost and permission implications), no annotations, and no output schema, the description is insufficient. It doesn't address behavioral aspects, error handling, or what the tool returns upon success/failure. The agent would need to guess about important operational details.

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 all three parameters clearly documented in the input schema. The description adds no additional parameter information beyond what's in the schema (e.g., no examples, format details, or constraints). According to the rules, when schema coverage is high (>80%), the baseline score is 3 even without param info in the description.

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 ('Create') and resource ('a new DynamoDB table'), making the purpose immediately understandable. It distinguishes from siblings like 'dynamodb_table_delete' or 'dynamodb_table_update' by specifying creation. However, it doesn't explicitly differentiate from 's3_bucket_create' or other resource creation tools, which keeps it from a perfect score.

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. It doesn't mention prerequisites (e.g., needing proper AWS permissions), when to choose this over updating an existing table, or how it relates to sibling tools like 'dynamodb_table_list' for checking existing tables. This leaves the agent with minimal context for decision-making.

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