Add to Docker Desktop
Version 4.43 or later needs to be installed to add the server automatically
Tools
| Name | Description |
|---|---|
dynamodb_data_model_schema_converter | Retrieves the DynamoDB Data Model Schema Converter Expert prompt. This tool returns a specialized prompt for converting DynamoDB data models (dynamodb_data_model.md) into schema.json - a structured JSON representation used for generating type-safe entities and repositories. By default, also includes instructions for generating usage_data.json with realistic sample data. The prompt guides through: - Reading and parsing dynamodb_data_model.md files - Converting table designs, GSIs, and access patterns into structured JSON format - Validating generated schemas using the dynamodb_data_model_schema_validator tool - Iteratively fixing validation errors (up to 8 iterations) - Generating usage_data.json with realistic sample data from markdown tables (unless generate_usage_data=False) - Creating isolated output folders with schema.json (and optionally usage_data.json) When to set generate_usage_data=False: - User explicitly asks for "schema only", "just schema", "without usage data", "without examples" - User wants to skip sample data generation - User only needs the schema structure for validation or review |
dynamodb_data_model_schema_validator | Validates a schema.json file - the structured JSON representation of your DynamoDB data model. This tool validates that your schema.json file is properly formatted and contains all required fields for use with the repository generation tool and other automation tools. It provides detailed error messages with suggestions for fixing any issues found. Optionally, if usage_data_path is provided, it will also validate the usage_data.json file against the schema to ensure consistency. The validation checks: - Required sections (table_config, entities) exist - All required fields are present - Field types are valid (string, integer, decimal, boolean, array, object, uuid) - Enum values are correct (operation types, return types, etc.) - Pattern IDs are unique across all entities - GSI names match between gsi_list and gsi_mappings - Fields referenced in templates exist in entity fields - Range conditions are valid and have correct parameter counts - Access patterns have valid operations and return types - Usage data validation (if usage_data_path provided) Security: - Schema files must be within the current working directory or subdirectories - Path traversal attempts (e.g., ../../../../etc/passwd) are blocked |